Networkable digital life jackets and associated methods

ABSTRACT

Networkable digital life jackets and associated methods are disclosed. An example life jacket includes a state manager and a swarm manager. The state manager is configured to selectively operate the life jacket in one of multiple operational states of the life jacket based on data obtained from one or more sensors of the life jacket. The swarm manager is configured to form a swarm network including the life jacket and one or more other life jackets.

FIELD OF THE DISCLOSURE

This disclosure relates generally to life jackets and, morespecifically, to networkable digital life jackets and associatedmethods.

BACKGROUND

Vehicles configured to travel over, on and/or under water and stationstructures such as offshore platforms are commonly equipped with lifejackets that are available to be worn by the passengers of the vehicle.For example, commercial aircraft are commonly equipped with passengerlife jackets that are stowed aboard (e.g., under the passenger seats of)the aircraft. In some known vehicle-based life jacket implementations,each life jacket stowed aboard the vehicle includes a radio frequencyidentification (RFID) tag attached to and/or embedded within the lifejacket that can actively and/or passively inform an interrogation device(e.g., an RFID scanner) of the status of the life jacket. For example,in some such implementations, information obtainable via the RFID tag ofeach life jacket can include a unique identifier, an assigned storagelocation, a current location, and/or an expiration date of the lifejacket. Such information can be used by the interrogation device tomonitor the location status and/or the health status of the life jacket.

SUMMARY

Networkable digital life jackets and associated methods are disclosedherein. In some examples, a life jacket is disclosed. In some disclosedexamples, the life jacket includes a state manager and a swarm manager.In some disclosed examples, the state manager is configured toselectively operate the life jacket in one of multiple operationalstates of the life jacket based on data obtained from one or moresensors of the life jacket. In some disclosed examples, the swarmmanager is configured to form a swarm network including the life jacketand one or more other life jackets.

In some examples, a method is disclosed. In some disclosed examples, themethod includes selectively operating a life jacket, by executing acomputer-readable instruction with one or more processors of the lifejacket, in one of multiple operational states of the life jacket basedon data obtained from one or more sensors of the life jacket. In somedisclosed examples, the method further includes forming a swarm networkincluding the life jacket and one or more other life jackets.

In some examples, a non-transitory computer-readable medium includinginstructions is disclosed. In some disclosed examples, the instructions,when executed, cause one or more processors of a life jacket toselectively operate the life jacket in one of multiple operationalstates of the life jacket based on data obtained from one or moresensors of the life jacket. In some disclosed examples, theinstructions, when executed, further cause the one or more processors toform a swarm network including the life jacket and one or more otherlife jackets.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a first example environment in which one or moreexample life jacket(s) can be implemented in accordance with teachingsof this disclosure.

FIG. 2 illustrates a second example environment in which the examplelife jacket(s) of FIG. 1 can be implemented in accordance with teachingsof this disclosure

FIG. 3 is a block diagram of an example life jacket constructed inaccordance with teachings of this disclosure.

FIG. 4 illustrates an example state diagram that can be implemented bythe example state manager of the example life jacket of FIG. 3.

FIG. 5A illustrates an example aircraft fuselage section includingexample life jackets from which one or more example swarm networks canbe formed.

FIG. 5B illustrates another example aircraft fuselage section includingexample life jackets.

FIG. 6 illustrates an example swarm network operating in an environmentin which several example life jackets of the swarm network are immersedin water.

FIG. 7 illustrates a first example swarm network communication diagram.

FIG. 8 illustrates a second example swarm network communication diagram.

FIG. 9 is a flowchart representative of example machine-readableinstructions that can be executed to implement the example life jacketof FIG. 3 to selectively operate the life jacket in one of multipleoperational states of the life jacket.

FIG. 10 is a flowchart representative of example machine-readableinstructions that can be executed to implement the example life jacketof FIG. 3 to generate and transmit status data for the life jacket.

FIG. 11 is a flowchart representative of example machine-readableinstructions that can be executed to implement the example life jacketof FIG. 3 to generate and utilize a swarm network including the lifejacket.

FIG. 12 is a block diagram of an example processor platform structuredto execute the example machine-readable instructions of FIGS. 9-11 toimplement the example life jacket of FIG. 3.

Certain examples are shown in the above-identified figures and describedin detail below. In describing these examples, identical referencenumbers are used to identify the same or similar elements. The figuresare not necessarily to scale and certain features and certain views ofthe figures may be shown exaggerated in scale or in schematic forclarity and/or conciseness.

Descriptors “first,” “second,” “third,” etc. are used herein whenidentifying multiple elements or components which may be referred toseparately. Unless otherwise specified or understood based on theircontext of use, such descriptors are not intended to impute any meaningof priority or ordering in time but merely as labels for referring tomultiple elements or components separately for ease of understanding thedisclosed examples. In some examples, the descriptor “first” may be usedto refer to an element in the detailed description, while the sameelement may be referred to in a claim with a different descriptor suchas “second” or “third.” In such instances, it should be understood thatsuch descriptors are used merely for ease of referencing multipleelements or components.

DETAILED DESCRIPTION

In some known vehicle-based life jacket implementations, each lifejacket stowed aboard the vehicle includes a radio frequencyidentification (RFID) tag attached to and/or embedded within the lifejacket that can actively and/or passively inform an interrogation device(e.g., an RFID scanner) of the status of the life jacket. For example,in some such implementations, information obtainable via the RFID tag ofeach life jacket can include a unique identifier, an assigned storagelocation, a current location, and/or an expiration date of the lifejacket. Such information can be used by the interrogation device tomonitor the location status and/or the health status of the life jacket.

The known vehicle-based life jacket implementations described above havenumerous shortcomings. For example, the amount and/or type of data thatcan be communicated from each life jacket is relatively limited andnon-informative relative to events that may occur in association withthe maintenance and/or use of the life jacket. As another example, thelife jackets of such known implementations lack the ability tocommunicate with one another, and/or to form a communication networkincluding each other.

Example networkable digital life jackets and associated methods aredisclosed herein. Unlike the known life jackets and/or knownvehicle-based life jacket implementations described above, life jacketsof the known implementations, example digital life jackets disclosedherein advantageously include an array and/or collection of sensor(s)and/or processing element(s) that are individually and/or collectivelyconfigured to determine and/or generate transmittable status dataindicating whether the life jacket has moved (e.g., relative to anassigned storage location) by more than a threshold amount, whether thelife jacket has been installed (e.g., placed on and/or connected to) auser, whether the life jacket has been immersed in water, and/or userhealth status associated with a user wearing the life jacket. Suchdetailed status data can advantageously be transmitted from exampledigital life jackets disclosed herein to rescue vehicles and/or servicesto inform such rescue vehicles and/or services in a manner that can beof critical importance and/or assistance with regard to implementingefficient rescue efforts.

As another advantage, example digital life jackets disclosed herein arenetworkable with one another. In this regard, example digital lifejackets disclosed herein are advantageously structured and/or configuredto communicate with one another via a swarm network formed by two ormore of the life jackets. Example digital life jackets disclosed hereinidentify a lead life jacket (e.g., a gateway life jacket) for the swarmnetwork. The lead life jacket transmits swarm status data that includesstatus data for all members of the swarm network, thereby advantageouslyincreasing the efficiency of search and rescue efforts, and alsoadvantageously reducing the amount of power consumed by the non-leadmembers of the swarm network.

FIG. 1 illustrates a first example environment 100 in which one or moreexample life jacket(s) can be implemented in accordance with teachingsof this disclosure. In the illustrated example of FIG. 1, the firstenvironment 100 includes a first example life jacket 102, a secondexample life jacket 104, and a third example life jacket 106. The firstlife jacket 102 is located and/or stowed at a first example seat 108,the second life jacket 104 is located and/or stowed at a second exampleseat 110, and the third life jacket 106 is located and/or stowed at athird example seat 112. In the illustrated example of FIG. 1, the firstenvironment 100 is located within a fuselage of an aircraft, and each ofthe first, second and third seats 108, 110, 112 is a seat (e.g., apassenger seat) of the aircraft. In other examples, the firstenvironment 100 can instead be located within a different structureand/or a different type of vehicle having seats. In still otherexamples, the first environment 100 can instead be an environment thatis not located within a vehicle.

As further shown in the illustrated example of FIG. 1, the firstenvironment 100 also includes a device 114 located remotely from each ofthe first, second and third life jackets 102, 104, 106. In theillustrated example of FIG. 1, the device 114 is a smartphone. In otherexamples, the device can instead be a tablet, a laptop computer, adesktop computer, a server, another life jacket, a rescue vehicle, acellular base station, a wireless access point, etc. Each of the first,second and third life jackets 102, 104, 106 of FIG. 1 includes atransceiver or other suitable communication device that is configured tocommunicate (e.g., wirelessly communicate) with the device 114 for thepurpose of providing the device 114 with status data associated with thelife jacket. For example, the first life jacket 102 can transmit statusdata to the device 114 including a unique identifier (e.g., ID No.1234), an expiration date (e.g., Dec. 31, 2020), an assigned storagelocation (e.g., Seat No. 11A), and a current location (e.g., at Seat No.11A) of the first life jacket 102. As another example, the second lifejacket 104 can transmit status data to the device 114 including a uniqueidentifier (e.g., ID No. 1235), an expiration date (e.g., Dec. 31,2020), an assigned storage location (e.g., Seat No. 11B), and a currentlocation (e.g., at Seat No. 11B) of the second life jacket 104. Asanother example, the third life jacket 106 can transmit status data tothe device 114 including a unique identifier (e.g., ID No. 2110), anexpiration date (e.g., Jun. 30, 2021), an assigned storage location(e.g., Seat No. 11C), and a current location (e.g., at Seat No. 11C) ofthe third life jacket 106.

Each of the first, second and third life jackets 102, 104, 106 of FIG. 1further includes an array and/or collection of sensor(s) and/orprocessing element(s) that are individually and/or collectivelyconfigured to determine whether the life jacket has moved (e.g.,relative to its assigned storage location) by more than a thresholdamount, whether the life jacket has been installed (e.g., placed onand/or connected to) a user, and/or whether the life jacket has beenimmersed in water. In some examples, the sensor(s) of each of the first,second and third life jackets 102, 104, 106 include(s) a motion sensor,an accelerometer, an ambient temperature sensor, a buckle sensor, amoisture sensor, a body temperature sensor, a pulse sensor, and/or arespiration sensor. In some examples, the processing element(s) of eachof the first, second and third life jackets 102, 104, 106 is/areimplemented as one or more processor(s), microprocessor(s),controller(s) and/or microcontroller(s), and can include a jacket healthevaluator, a movement evaluator, an installation evaluator, an immersionevaluator, a user health evaluator, and/or a battery evaluatorconfigured to evaluate data sensed, measured and/or detected by, and/orobtained from, the aforementioned sensor(s).

In some examples, the processing element(s) of each of the first, secondand third life jackets 102, 104, 106 of FIG. 1 additionally oralternatively include(s) a state manager configured to selectivelyoperate the life jacket in one of multiple operational states of thelife jacket including a stowed (e.g., latent) state and one or more of amotion state, an installed state, or a immersed state. In some examples,the processing element(s) of each of the first, second and third lifejackets 102, 104, 106 of FIG. 1 additionally or alternatively include(s)a status manager configured to generate status data for the life jacket.In such examples, each of the first, second and third life jackets 102,104, 106 further includes a radio transmitter to transmit the statusdata to the device 114, and/or to another device that may or may not belocated within the first environment 100 of FIG. 1. In some suchexamples, the status data includes jacket health data generated by thejacket health evaluator, movement data generated by the movementevaluator, installation data generated by the installation evaluator,immersion data generated by the immersion evaluator, user health datagenerated by the user health evaluator, battery energy data generated bythe battery evaluator, and/or operational state data generated by thestate manager of the life jacket.

FIG. 2 illustrates a second example environment 200 in which the examplelife jacket(s) of FIG. 1 can be implemented in accordance with teachingsof this disclosure. The second environment 200 of FIG. 2 includes eachof the first, second and third life jackets 102, 104, 106 of FIG. 1described above, structured and/or configured in the same manner asdescribed above in connection with FIG. 1. In some examples, theprocessing element(s) of each of the first, second and third lifejackets 102, 104, 106 of FIGS. 1 and 2 additionally or alternativelyinclude(s) a swarm manager configured to form a swarm network includingtwo or more of the first, second and third life jackets 102, 104, 106.For example, as shown in FIG. 2, the second environment 200 includes anexample swarm network 202 formed by and/or including each of the first,second and third life jackets 102, 104, 106.

In some examples, the swarm manager of each of the first, second andthird life jackets 102, 104, 106 is further configured to identify alead life jacket of the swarm network 202 from among the first, secondand third life jackets 102, 104, 106. In the illustrated example of FIG.2, the first life jacket 102 has been identified as an example lead lifejacket 204 of the swarm network 202. In some examples, the lead lifejacket 204 transmits swarm status data from the lead life jacket 204 toan example remotely located device 206 (e.g., a rescue vehicle). In suchexamples, the swarm status data includes status data for the lead lifejacket 204 (e.g., the first life jacket 102), as well as for each of thenon-lead life jackets (e.g., the second and third life jackets 104, 106)that form the swarm network 202. The formation of the swarm network 202and/or the transmission of the swarm status data from the lead lifejacket 204 of the swarm network advantageously increasing the efficiencyof search and rescue efforts, and also advantageously reducing theamount of power consumed by the non-lead life jackets of the swarmnetwork.

FIG. 3 is a block diagram of an example life jacket 300 constructed inaccordance with teachings of this disclosure. The block diagram of FIG.3 can be used to implement any of the first, second and/or third examplelife jackets 102, 104, 106 of FIGS. 1 and 2. In the illustrated exampleof FIG. 3, the life jacket 300 includes an example battery 302, anexample GPS receiver 304, an example motion sensor 306, an exampleaccelerometer 308, an example ambient temperature sensor 310, an examplebuckle sensor 312, an example moisture sensor 314, an example bodytemperature sensor 316, an example pulse sensor 318, an examplerespiration sensor 320, an example jacket identifier 322, an examplelocation identifier 324, an example jacket health evaluator 326, anexample movement evaluator 328, an example installation evaluator 330,an example immersion evaluator 332, an example user health evaluator334, an example battery evaluator 336, an example state manager 338, anexample swarm manager 340, an example status manager 342, an exampleschedule manager 344, an example protocol manager 346, an example systeminterface 348, an example network interface 350, and an example memory352. The example system interface 348 of FIG. 3 includes one or moreexample input device(s) 354 and one or more example output device(s)356. The example network interface 350 of FIG. 3 includes an exampleradio transmitter 358 and an example radio receiver 360. However, otherexample implementations of the life jacket 300 of FIG. 3 can includefewer or additional structures.

In the illustrated example of FIG. 3, the battery 302, the GPS receiver304, the motion sensor 306, the accelerometer 308, the ambienttemperature sensor 310, the buckle sensor 312, the moisture sensor 314,the body temperature sensor 316, the pulse sensor 318, the respirationsensor 320, the jacket identifier 322, the location identifier 324, thejacket health evaluator 326, the movement evaluator 328, theinstallation evaluator 330, the immersion evaluator 332, the user healthevaluator 334, the battery evaluator 336, the state manager 338, theswarm manager 340, the status manager 342, the schedule manager 344, theprotocol manager 346, the system interface 348 (including the inputdevice(s) 354 and the output device(s) 356), the network interface 350(including the radio transmitter 358 and the radio receiver 360), and/orthe memory 352 are operatively coupled (e.g., in electricalcommunication) via an example communication bus 362. The jacketidentification identifier 322, the location identifier 324, the jackethealth evaluator 326, the movement evaluator 328, the installationevaluator 330, the immersion evaluator 332, the user health evaluator334, the battery evaluator 336, the state manager 338, the swarm manager340, the status manager 342, the schedule manager 344, and/or theprotocol manager 346 of FIG. 3 can individually and/or collectively beimplemented by any type(s) and/or any number(s) of semiconductordevice(s) (e.g., processor(s), microprocessor(s), controller(s),microcontroller(s), etc.).

The battery 302 of FIG. 3 stores energy. In some examples, the battery302 provides and/or supplies power to the GPS receiver 304, the motionsensor 306, the accelerometer 308, the ambient temperature sensor 310,the buckle sensor 312, the moisture sensor 314, the body temperaturesensor 316, the pulse sensor 318, the respiration sensor 320, the jacketidentifier 322, the location identifier 324, the jacket health evaluator326, the movement evaluator 328, the installation evaluator 330, theimmersion evaluator 332, the user health evaluator 334, the batteryevaluator 336, the state manager 338, the swarm manager 340, the statusmanager 342, the schedule manager 344, the protocol manager 346, thesystem interface 348 (including the input device(s) 354 and the outputdevice(s) 356), the network interface 350 (including the radiotransmitter 358 and the radio receiver 360), and/or the memory 352 ofthe life jacket 300 of FIG. 3. As power is provided by the battery 302,the energy stored by the battery 302 is consumed. In some examples, thebattery 302 of FIG. 3 can be implemented as a rechargeable battery thatharvests power (e.g., to recharge and/or to maintain a fully-chargedstate) from a host device to which the battery 302 is removably coupled.For example, the battery 302 can be removably coupled to a poweredelectrical port of a vehicle seat (e.g., an aircraft seat) at which thelife jacket 300 of FIG. 3 is removably stowed. In other examples, thebattery 302 can harvest power from vibrations and/or movements of thestructure (e.g., a seat), the vehicle (e.g. an aircraft), and/or theuser (e.g., a human wearer) to which the life jacket 300 of FIG. 3 iscoupled.

The GPS receiver 304 of FIG. 3 collects, acquires and/or receives dataand/or one or more signal(s) from one or more GPS satellite(s).Typically, signals from three or more satellites are needed to form theGPS triangulation. The data and/or signal(s) received by the GPSreceiver 304 can include information (e.g., time stamps) from which thecurrent position and/or location of the life jacket 300 can beidentified and/or derived, including for example, the current latitude,longitude and altitude of the life jacket 300. Location data identifiedand/or derived from the signal(s) collected and/or received by the GPSreceiver 304 can be associated with one or more local time(s) (e.g.,time stamped) at which the data and/or signal(s) were collected and/orreceived by the GPS receiver 304. Location data identified and/orderived from the signal(s) collected and/or received by the GPS receiver304 can be of any quantity, type, form and/or format, and can be storedin a computer-readable storage medium such as the example memory 352 ofFIG. 3 described below.

The motion sensor 306 of FIG. 3 senses, measures and/or detects motion(e.g., movements, changes in position, changes in orientation, etc.) ofthe life jacket 300 of FIG. 3. For example, the motion sensor 306 cansense, measure and/or detect movement (e.g., removal) of the life jacket300 from a stowed position (e.g., an assigned seat position). The motionsensor 306 can be implemented by any number (e.g., 1, 2, 3, etc.) ofdepth sensors, proximity sensors, acoustic sensors, accelerometers,gyroscopes, compasses, and/or other motion-sensing devices. Motion datasensed, measured and/or detected by the motion sensor 306 can beassociated with one or more local time(s) (e.g., time stamped) at whichthe data was collected by the motion sensor 306. Motion data sensed,measured and/or detected by the motion sensor 306 can be of anyquantity, type, form and/or format, and can be stored in acomputer-readable storage medium such as the example memory 352 of FIG.3 described below.

The accelerometer 308 of FIG. 3 senses, measures and/or detects changesin velocity (e.g., acceleration(s)) of the life jacket 300 of FIG. 3.Different changes in the velocity values sensed, measured and/ordetected by the accelerometer 308 correspond to different accelerationsof the life jacket 300. In some examples, the accelerometer 308 of FIG.3 can be implemented as a triple-axis accelerometer (e.g., a 3-axisaccelerometer) such that the accelerometer 308 senses, measures and/ordetects acceleration data for each of three axes of a coordinate systemassociated with the life jacket 300. Acceleration data sensed, measuredand/or detected by the accelerometer 308 can be associated with one ormore local time(s) (e.g., time stamped) at which the data was collectedby the accelerometer 308. Acceleration data sensed, measured and/ordetected by the accelerometer 308 can be of any quantity, type, formand/or format, and can be stored in a computer-readable storage mediumsuch as the example memory 352 of FIG. 3 described below.

The ambient temperature sensor 310 of FIG. 3 senses, measures and/ordetects the ambient temperature of the life jacket 300 of FIG. 3. Forexample, the ambient temperature sensor 310 can sense, measure and/ordetect the ambient temperature of the life jacket 300 when the lifejacket is in a stowed position, and/or when the life jacket is installedon (e.g., worn by) a user. The ambient temperature sensor 310 can beimplemented by any number (e.g., 1, 2, 3, etc.) of thermostats,thermistors, thermocouples, and/or other temperature-sensing devices.Ambient temperature data sensed, measured and/or detected by the ambienttemperature sensor 310 can be associated with one or more local time(s)(e.g., time stamped) at which the data was collected by the ambienttemperature sensor 310. Ambient temperature data sensed, measured and/ordetected by the ambient temperature sensor 310 can be of any quantity,type, form and/or format, and can be stored in a computer-readablestorage medium such as the example memory 352 of FIG. 3 described below.

The buckle sensor 312 of FIG. 3 senses and/or detects whether the lifejacket 300 of FIG. 3 is buckled. The buckle sensor 312 can beimplemented by any number (e.g., 1, 2, 3, etc.) of mechanical and/orelectrical sensors configured to sense and/or detect the fastening,securing and/or connecting of a latch element (e.g., a clip) of the lifejacket 300 to a corresponding buckle element (e.g., a clip receptacle)of the life jacket 300. Buckle connection data sensed, measured and/ordetected by the buckle sensor 312 can be associated with one or morelocal time(s) (e.g., time stamped) at which the data was collected bythe buckle sensor 312. Buckle connection data sensed, measured and/ordetected by the buckle sensor 312 can be of any quantity, type, formand/or format, and can be stored in a computer-readable storage mediumsuch as the example memory 352 of FIG. 3 described below.

The moisture sensor 314 of FIG. 3 senses, measures and/or detects theextent to which the life jacket 300 of FIG. 3 is exposed to water. Themoisture sensor 314 can be implemented by any number (e.g., 1, 2, 3,etc.) of chemical, mechanical and/or electrical sensors configured tosense and/or detect moisture and/or humidity associated with the lifejacket 300. Moisture data sensed, measured and/or detected by themoisture sensor 314 can be associated with one or more local time(s)(e.g., time stamped) at which the data was collected by the moisturesensor 314. Moisture data sensed, measured and/or detected by themoisture sensor 314 can be of any quantity, type, form and/or format,and can be stored in a computer-readable storage medium such as theexample memory 352 of FIG. 3 described below.

The body temperature sensor 316 of FIG. 3 senses, measures and/ordetects the body temperature of a user wearing the life jacket 300 ofFIG. 3. The body temperature sensor 316 can be implemented by any number(e.g., 1, 2, 3, etc.) of thermostats, thermistors, thermocouples, and/orother temperature-sensing devices. In some examples, the bodytemperature sensor 316 of FIG. 3 is a contact-type temperature sensorthat is configured to contact one or more body surface(s) of a user whenthe life jacket 300 of FIG. 3 is worn by the user. Body temperature datasensed, measured and/or detected by the body temperature sensor 316 canbe associated with one or more local time(s) (e.g., time stamped) atwhich the data was collected by the body temperature sensor 316. Bodytemperature data sensed, measured and/or detected by the bodytemperature sensor 316 can be of any quantity, type, form and/or format,and can be stored in a computer-readable storage medium such as theexample memory 352 of FIG. 3 described below.

The pulse sensor 318 of FIG. 3 senses, measures and/or detects the pulse(e.g., heart rate) of a user wearing the life jacket 300 of FIG. 3. Thepulse sensor 318 can be implemented by any number (e.g., 1, 2, 3, etc.)of electrocardiography sensors and/or other pulse-sensing orheart-rate-sensing devices. In some examples, the pulse sensor 318 ofFIG. 3 is a contact-type pulse sensor that is configured to contact oneor more body surface(s) of a user when the life jacket 300 of FIG. 3 isworn by the user. Pulse data sensed, measured and/or detected by thepulse sensor 318 can be associated with one or more local time(s) (e.g.,time stamped) at which the data was collected by the pulse sensor 318.Pulse data sensed, measured and/or detected by the pulse sensor 318 canbe of any quantity, type, form and/or format, and can be stored in acomputer-readable storage medium such as the example memory 352 of FIG.3 described below.

The respiration sensor 320 of FIG. 3 senses, measures and/or detects therespiration (e.g., breathing rate) of a user wearing the life jacket 300of FIG. 3. The respiration sensor 320 can be implemented by any number(e.g., 1, 2, 3, etc.) of spirometer sensors and/or otherrespiration-sensing or breathing-rate-sensing devices. In some examples,the respiration sensor 320 of FIG. 3 is a contact-type respirationsensor that is configured to contact one or more body surface(s) of auser when the life jacket 300 of FIG. 3 is worn by the user. Respirationdata sensed, measured and/or detected by the respiration sensor 320 canbe associated with one or more local time(s) (e.g., time stamped) atwhich the data was collected by the respiration sensor 320. Respirationdata sensed, measured and/or detected by the respiration sensor 320 canbe of any quantity, type, form and/or format, and can be stored in acomputer-readable storage medium such as the example memory 352 of FIG.3 described below

The jacket identifier 322 of FIG. 3 identifies and/or determines aunique identifier of the life jacket 300, an assigned storage location(e.g., the intended stowed position) of the life jacket 300, and/or anexpiration date of the life jacket 300. For example, the jacketidentifier 322 can identify and/or determine a unique identifier (e.g.,a serial number) of the life jacket 300 that differentiates the lifejacket 300 from other life jackets. As another example, the jacketidentifier 322 can additionally or alternatively identify and/ordetermine an assigned position, location and/or object (e.g., a seatnumber) at which the life jacket 300 is stowed (or is to be stowed). Asanother example, the jacket identifier 322 can additionally oralternatively identify and/or determine an expiration date (e.g., anexpressly-defined expiration date, or an expiration date establishedbased on an expressly-defined date of manufacture) of the life jacket300.

In some examples, the jacket identifier 322 of FIG. 3 can identifyand/or determine the unique identifier, the assigned storage location,and/or the expiration date of the life jacket 300 by accessing and/orobtaining the unique identifier, the assigned storage location, and/orthe expiration date from the memory 352 of the life jacket 300. In otherexamples, the jacket identifier 322 can additionally or alternativelyidentify and/or determine the unique identifier, the assigned storagelocation, and/or the expiration date of the life jacket 300 based on oneor more input(s) received via the input device(s) 354 of the systeminterface 348 of FIG. 3, and/or based on one or more communication(s)received via the radio receiver 360 of the network interface 350 of FIG.3.

The location identifier 324 of FIG. 3 identifies and/or determines thelocation (e.g., the current location) of the life jacket 300 of FIG. 3.For example, the location identifier 324 of FIG. 3 can identify and/ordetermine the location of the life jacket 300 of FIG. 3 by deriving thecurrent location from the data and/or signal(s) received by the GPSreceiver 304 of FIG. 3. In some examples, the location of the lifejacket 300 identified and/or determined by the location identifier 324includes the current latitude, the current longitude, and/or the currentaltitude of the life jacket 300. Location data identified, determinedand/or processed by and/or at the location identifier 324 can be of anyquantity, type, form and/or format, and can be stored in acomputer-readable storage medium such as the example memory 352 of FIG.3 described below.

The jacket health evaluator 326 of FIG. 3 evaluates and/or monitors thehealth (e.g., the remaining lifespan) of the life jacket 300 of FIG. 3.For example, the jacket health evaluator 326 can evaluate and/or monitorthe health of the life jacket 300 based on the expiration dateidentified and/or determined by the jacket identifier 322 of FIG. 3. Insome examples, the jacket health evaluator 326 compares the expirationdate identified and/or determined by the jacket identifier 322 to acurrent (e.g., actual) date identified and/or determined by the jackethealth evaluator 326. In some such examples, the jacket health evaluator326 generates jacket health data (e.g., one or more jacket healthnotification(s)) based on the result and/or outcome of theaforementioned comparison.

For example, the jacket health evaluator 326 can generate first jackethealth data (e.g., indicating that the life jacket 300 is in good healthand/or has not expired) in response to the jacket health evaluator 326determining that the expiration date associated with the life jacket 300extends beyond the current date. As another example, the jacket healthevaluator 326 can additionally or alternatively generate second jackethealth data (e.g., indicating that the life jacket 300 is in poor healthand/or has expired) in response to the jacket health evaluator 326determining that the expiration date associated with the life jacket 300does not extend beyond the current date. Jacket health evaluation dataand/or jacket health data evaluated, generated and/or processed byand/or at the jacket health evaluator 326 can be of any quantity, type,form and/or format, and can be stored in a computer-readable storagemedium such as the example memory 352 of FIG. 3 described below.

The movement evaluator 328 of FIG. 3 evaluates and/or monitors movement(e.g., changes in position, changes in orientation, changes in velocity,etc.) of the life jacket 300 of FIG. 3. For example, the movementevaluator 328 can evaluate and/or monitor movement of the life jacket300 based on the motion data sensed, measured and/or detected by themotion sensor 306 of FIG. 3, and/or based on the acceleration datasensed, measured and/or detected by the accelerometer 308 of FIG. 3. Insome examples, the movement evaluator 328 compares the motion data to amotion threshold, and/or compares the acceleration data to anacceleration threshold. In some such examples, the movement evaluator328 generates movement data (e.g., one or more movement notification(s))based on the result(s) and/or outcome(s) of the aforementionedcomparison(s).

For example, the movement evaluator 328 can generate first movement data(e.g., indicating that the life jacket 300 has not moved by more than athreshold amount) in response to the movement evaluator 328 determiningthat the motion data is below the motion threshold, and/or that theacceleration data is below the acceleration threshold. As anotherexample, the movement evaluator 328 can additionally or alternativelygenerate second movement data (e.g., indicating that the life jacket 300has moved by more than a threshold amount) in response to the movementevaluator 328 determining that the motion data is equal to or above themotion threshold, and/or that the acceleration data is equal to or abovethe acceleration threshold.

In some examples, the movement evaluator 328 can evaluate and/or monitormovements of the life jacket 300 relative to the assigned storagelocation of the life jacket 300 identified and/or determined by thejacket identifier 322. In other examples, the movement evaluator 328 canadditionally and/or alternatively evaluate and/or monitor movements ofthe life jacket 300 relative to one or more location(s) of one or moreother life jacket(s). Movement evaluation data and/or movement dataevaluated, generated and/or processed by and/or at the movementevaluator 328 can be of any quantity, type, form and/or format, and canbe stored in a computer-readable storage medium such as the examplememory 352 of FIG. 3 described below.

The installation evaluator 330 of FIG. 3 evaluates and/or monitors theinstallation status of the life jacket 300 of FIG. 3. For example, theinstallation evaluator 330 can evaluate and/or monitor the installationstatus of the life jacket 300 based on the ambient temperature datasensed, measured and/or detected by the ambient temperature sensor 310of FIG. 3, and/or based on the buckle connection data sensed, measuredand/or detected by the buckle sensor 312 of FIG. 3. In some examples,the installation evaluator 330 compares the ambient temperature data toan ambient temperature threshold, and/or determines whether the buckleconnection data is indicative of a first (e.g., unbuckled) state or asecond (e.g., buckled) state. In some such examples, the installationevaluator 330 generates installation data (e.g., one or moreinstallation notification(s)) based on the result(s) and/or outcome(s)of the aforementioned comparison and/or determination.

For example, the installation evaluator 330 can generate firstinstallation data (e.g., indicating that the life jacket 300 has notbeen installed on the body of a user) in response to the installationevaluator 330 determining that the ambient temperature data is below theambient temperature threshold, and/or that the buckle connection dataindicates an unbuckled state. As another example, the installationevaluator 330 can additionally or alternatively generate secondinstallation data (e.g., indicating that the life jacket 300 has beeninstalled on the body of a user) in response to the installationevaluator 330 determining that the ambient temperature data is equal toor above the ambient temperature threshold, and/or that the buckleconnection data indicates a buckled state. Installation evaluation dataand/or installation data evaluated, generated and/or processed by and/orat the installation evaluator 330 can be of any quantity, type, formand/or format, and can be stored in a computer-readable storage mediumsuch as the example memory 352 of FIG. 3 described below.

The immersion evaluator 332 of FIG. 3 evaluates and/or monitors theimmersion status of the life jacket 300 of FIG. 3. For example, theimmersion evaluator 332 can evaluate and/or monitor the immersion statusof the life jacket 300 (e.g., whether or not the life jacket 300 hasbeen immersed in water) based on the moisture data sensed, measuredand/or detected by the moisture sensor 314 of FIG. 3. In some examples,the immersion evaluator 332 determines whether the moisture data isindicative of a first (e.g., non-immersed and/or dry) state or a second(e.g., immersed and/or wet) state. In some such examples, the immersionevaluator 332 generates immersion data (e.g., one or more immersionnotification(s)) based on the result and/or outcome of theaforementioned determination.

For example, the immersion evaluator 332 can generate first immersiondata (e.g., indicating that the life jacket 300 has not been immersed inwater) in response to the immersion evaluator 332 determining that themoisture data indicates a non-immersed (e.g., dry) state. As anotherexample, the immersion evaluator 332 can additionally or alternativelygenerate second immersion data (e.g., indicating that the life jacket300 has been immersed in water) in response to the immersion evaluator332 determining that the moisture data indicates an immersed (e.g., wet)state. Immersion evaluation data and/or immersion data evaluated,generated and/or processed by and/or at the immersion evaluator 332 canbe of any quantity, type, form and/or format, and can be stored in acomputer-readable storage medium such as the example memory 352 of FIG.3 described below.

The user health evaluator 334 of FIG. 3 evaluates and/or monitors thehealth of a user wearing the life jacket 300 of FIG. 3. For example, theuser health evaluator 334 can evaluate and/or monitor the health of auser wearing the life jacket 300 based on the body temperature datasensed, measured and/or detected by the body temperature sensor 316 ofFIG. 3, based on the pulse data sensed, measured and/or detected by thepulse sensor 318 of FIG. 3, and/or based on the respiration data sensed,measured and/or detected by the respiration sensor 320 of FIG. 3. Insome examples, the user health evaluator 334 compares the bodytemperature data to a body temperature threshold, compares the pulsedata to a pulse threshold, and/or compares the respiration data to arespiration threshold. In some such examples, the user health evaluator334 generates user health data (e.g., one or more user healthnotification(s)) based on the result(s) and/or outcome(s) of theaforementioned comparison(s).

For example, the user health evaluator 334 can generate first userhealth data (e.g., indicating that the user of the life jacket 300 is ingood health) in response to the user health evaluator 334 determiningthat the body temperature data is above the body temperature threshold,that the pulse data is above the pulse threshold, and/or that therespiration data is above the respiration threshold. As another example,the user health evaluator 334 can additionally or alternatively generatesecond user health data (e.g., indicating that the user of the lifejacket 300 is in poor health) in response to the user health evaluator334 determining that the body temperature data is equal to or below thebody temperature threshold, that the pulse data is equal to or below thepulse threshold, and/or that the respiration data is equal to or belowthe respiration threshold. User health evaluation data and/or userhealth data evaluated, generated and/or processed by and/or at the userhealth evaluator 334 can be of any quantity, type, form and/or format,and can be stored in a computer-readable storage medium such as theexample memory 352 of FIG. 3 described below.

The battery evaluator 336 of FIG. 3 evaluates and/or monitors theremaining energy (e.g., based on a current state of charge) of thebattery 302 of FIG. 3. In some examples, the battery evaluator 336compares the remaining energy of the battery 302 to an energy threshold.In some such examples, the battery evaluator 336 generates batteryenergy data (e.g., one or more battery energy notification(s)) based onthe result and/or outcome of the aforementioned comparison.

For example, the battery evaluator 336 can generate first battery energydata (e.g., indicating that the battery 302 of the life jacket 300 hassufficient remaining energy) in response to the battery evaluator 336determining that the remaining energy of the battery 302 is above theenergy threshold. As another example, the battery evaluator 336 cangenerate second battery energy data (e.g., indicating that the battery302 of the life jacket 300 does not have sufficient remaining energy) inresponse to the battery evaluator 336 determining that the remainingenergy of the battery 302 is equal to or below the energy threshold.Battery energy evaluation data and/or battery energy data evaluated,generated and/or processed by and/or at the battery evaluator 336 can beof any quantity, type, form and/or format, and can be stored in acomputer-readable storage medium such as the example memory 352 of FIG.3 described below.

The state manager 338 of FIG. 3 manages and/or controls one or moreoperational state(s) of the life jacket 300 of FIG. 3. For example, thestate manager 338 can selectively operate the life jacket 300 in one ofa stowed (e.g., latent) state, a motion state, an installed states, oran immersed state. In some such examples, the state manager 338 of FIG.3 operates the life jacket 300 in the stowed state while the life jacket300 is located at its assigned storage location, and/or prior to themovement evaluator 328 of FIG. 3 determining that the life jacket 300has moved by more than a threshold amount. The state manager 338additionally or alternatively operates the life jacket 300 in the motionstate in response to the movement evaluator 328 of FIG. 3 determiningthat the life jacket 300 has moved by more than a threshold amount,and/or prior to the installation evaluator 330 of FIG. 3 determiningthat the life jacket 300 has been installed on the body of a user. Thestate manager 338 additionally or alternatively operates the life jacket300 in the installed state in response to the installation evaluator 330of FIG. 3 determining that the life jacket 300 has been installed on thebody of a user, and/or prior to the immersion evaluator 332 of FIG. 3determining that the life jacket 300 has been immersed in water. Thestate manager 338 additionally or alternatively operates the life jacket300 in the immersed state in response to the immersion evaluator 332 ofFIG. 3 determining that the life jacket 300 has been immersed in water.

In some examples, the state manager 338 of FIG. 3 enables and/oractivates specific sensors and/or processing units of the life jacket300 of FIG. 3 based on and/or in response to the operational state ofthe life jacket 300. For example, the state manager 338 can enableand/or activate the GPS receiver 304, the motion sensor 306, theaccelerometer 308, the jacket identifier 322, the location identifier324, the jacket health evaluator 326, the movement evaluator 328, and/orthe battery evaluator 336 of FIG. 3 based on and/or in response to thelife jacket 300 being in the stowed (e.g., latent) state. As anotherexample, the state manager 338 can additionally enable and/or activatethe ambient temperature sensor 310, the buckle sensor 312, and/or theinstallation evaluator 330 of FIG. 3 based on and/or in response to thelife jacket 300 being in the motion state. As another example, the statemanager 338 can additionally enable and/or activate the moisture sensor314 and/or the immersion evaluator 332 of FIG. 3 based on and/or inresponse to the life jacket 300 being in the installed state. As anotherexample, the state manager 338 can additionally enable and/or activatethe body temperature sensor 316, the pulse sensor 318, the respirationsensor 320, and/or the user health evaluator 334 of FIG. 3 based onand/or in response to the life jacket 300 being in the immersed state.

In some examples, the state manager 338 of FIG. 3 disables and/ordeactivates specific sensors and/or processing units of the life jacket300 of FIG. 3 based on and/or in response to the operational state ofthe life jacket 300. For example, the state manager 338 can disableand/or deactivate the ambient temperature sensor 310, the buckle sensor312, the moisture sensor 314, the body temperature sensor 316, the pulsesensor 318, the respiration sensor 320, the installation evaluator 330,the immersion evaluator 332, and/or the user health evaluator 334 ofFIG. 3 based on and/or in response to the life jacket 300 being in thestowed (e.g., latent) state. As another example, the state manager 338can disable and/or deactivate the moisture sensor 314, the bodytemperature sensor 316, the pulse sensor 318, the respiration sensor320, the immersion evaluator 332, and/or the user health evaluator 334of FIG. 3 based on and/or in response to the life jacket 300 being inthe motion state. As another example, the state manager 338 can disableand/or deactivate the body temperature sensor 316, the pulse sensor 318,the respiration sensor 320, and/or the user health evaluator 334 of FIG.3 based on and/or in response to the life jacket 300 being in theinstalled state.

In some examples, the state manager 338 of FIG. 3 generates operationalstate data (e.g., one or more operational state notification(s)) basedon the operational state(s) of the life jacket 300 of FIG. 3. Forexample, the state manager 338 can generate first operational state data(e.g., indicating that the life jacket 300 is operating in the stowedstate) in response to the state manager 338 operating the life jacket300 in the stowed state. As another example, the state manager 338 cangenerate second operational state data (e.g., indicating that the lifejacket 300 is operating in the motion state) in response to the statemanager 338 operating the life jacket 300 in the motion state. Asanother example, the state manager 338 can generate third operationalstate data (e.g., indicating that the life jacket 300 is operating inthe installed state) in response to the state manager 338 operating thelife jacket 300 in the installed state. As another example, the statemanager 338 can generate fourth operational state data (e.g., indicatingthat the life jacket 300 is operating in the immersed state) in responseto the state manager 338 operating the life jacket 300 in the immersedstate. Operational state management data and/or operational state datamanaged, generated and/or processed by and/or at the state manager 338can be of any quantity, type, form and/or format, and can be stored in acomputer-readable storage medium such as the example memory 352 of FIG.3 described below.

FIG. 4 illustrates an example state diagram 400 that can be implementedby the example state manager 338 of the example life jacket 300 of FIG.3. As shown in FIG. 4, the life jacket 300 is selectively operable inone of an example stowed (e.g., latent) state 402, an example motionstate 404, an example installed state 406, and an example immersedstate. In the illustrated example of FIG. 4, the state diagram 400implemented by the state manager 338 enables the life jacket 300 totransition from the stowed state 402 to the motion state 404, from themotion state 404 to the installed state 406, and from the installedstate 406 to the immersed state 408. In other examples, the statemanager 338 can additionally or alternatively implement a state diagramthat enables the life jacket 300 to transition from the stowed state 402directly to the installed state 406, from the stowed state 402 directlyto the immersed state 408, and/or from the motion state 404 directly tothe immersed state 408.

In some examples, the state manager 338 of FIG. 3 causes the life jacket300 to transition between different states of the state diagram 400 ofFIG. 4 in response to determinations made by, and/or data generated by,one or more of the movement evaluator 328, the installation evaluator330, and/or the immersion evaluator 332 of FIG. 3. For example, thestate manager 338 can cause the life jacket 300 to transition from thestowed state 402 to the motion state 404 in response to the movementevaluator 328 determining that the life jacket 300 has moved more than athreshold amount. As another example, the state manager 338 can causethe life jacket 300 to transition from the motion state 404 to theinstallation state 406 in response to the installation evaluator 330determining that the life jacket 300 has been installed on a user. Asanother example, the state manager 338 can cause the life jacket 300 totransition from the installed state 406 to the immersed state 408 inresponse to the immersion evaluator 332 determining that the life jacket300 has been immersed in water.

Returning to the illustrated example of FIG. 3, the swarm manager 340 ofFIG. 3 manages and/or controls the formation and/or maintenance of aswarm network that includes the life jacket 300 of FIG. 3 and one ormore other life jacket(s). The swarm manager 340 can generate and/orform a swarm network between and/or among the life jacket 300 of FIG. 3and one or more other life jacket(s) at any time, and/or while the lifejacket 300 of FIG. 3 is configured in any state. For example, the swarmmanager 340 can generate and/or form a swarm network while the lifejacket 300 is in a stowed (e.g., latent) state. As another example, theswarm manager 340 can generate and/or form a swarm network while thelife jacket 300 is in a motion state, and/or in response to the lifejacket 300 transitioning from a stowed state to a motion state. Asanother example, the swarm manager 340 can generate and/or form a swarmnetwork while the life jacket 300 is in an installed state, and/or inresponse to the life jacket 300 transitioning from a motion state to aninstalled state. As another example, the swarm manager 340 can generateand/or form a swarm network while the life jacket 300 is in an immersedstate, and/or in response to the life jacket 300 transitioning from aninstalled state to an immersed state.

In some examples, a swarm network generated and/or formed by the swarmmanager 340 of FIG. 3 can include a group of life jackets that arelocated on a vehicle (e.g., on an aircraft) and are within aspatially-proximate distance from one another. For example, the swarmmanager 340 can generate and/or form a swarm network that includes alllife jackets located at ten consecutive rows of seating of an aircraft(e.g., all life jackets located at seating rows one through ten). Insome such examples, the life jackets to be included in the swarm networkare defined and/or determined by one or more swarm size, swarm shape,swarm pattern and/or swarm configuration policies implemented and/orapplied by the swarm manager 340. In other examples, a swarm networkgenerated and/or formed by the swarm manager 340 of FIG. 3 can include agroup of life jackets that are randomly located on a vehicle (e.g., onan aircraft). For example, the swarm manager 340 can generate and/orform a swarm network that includes a first life jacket located at afirst row of seating of an aircraft, a second life jacket located at athird row of seating of the aircraft, and a third life jacket located ata twentieth row of seating of an aircraft. In some such examples, thelife jackets to be included in the swarm network are randomly determinedby the swarm manager 340.

Each life jacket of a swarm network generated and/or formed by the swarmmanager 340 of FIG. 3 is structured and/or configured in a manner thatenables the life jacket to transmit and/or receive communications (e.g.,radio signals and/or data) to and/or from at least one of the other lifejacket(s) of the swarm network. For example, the life jacket 300 of FIG.3 includes a radio transmitter 358 to facilitate the transmission ofradio communications from the life jacket 300 to one or more other lifejacket(s) of a swarm network, and a radio receiver 360 to facilitate thereceiving of radio communications at the life jacket 300 from one ormore other life jacket(s) of a swarm network. In some examples, eachlife jacket of the swarm network is structured and/or configured in amanner that is substantially similar to the life jacket 300 of FIG. 3.

In connection with and/or in response to generating and/or forming aswarm network, the swarm manager 340 of FIG. 3 identifies and/ordetermines a lead life jacket (e.g., a gateway life jacket) from amongthe life jackets included in the swarm network. In some examples, theswarm manager 340 can identify the life jacket 300 of FIG. 3 as the leadlife jacket of the swarm network. In other examples, the swarm manager340 can alternatively identify one of the other life jacket(s) of theswarm network as the lead life jacket of the swarm network. In someexamples, the identification and/or designation of a lead life jacketfacilitates a reduction in the amount and/or the extent of batteryenergy to be consumed by the other (e.g., non-lead) life jackets of theswarm network.

The swarm manager 340 of FIG. 3 can identify and/or determine the leadlife jacket of a swarm network using one or more evaluation and/orselection technique(s). For example, the swarm manager 340 can identifyand/or determine the lead life jacket of the swarm network as the lifejacket from among the multiple life jackets of the swarm network thatdemonstrates the greatest signal strength for radio communications fromthe radio transmitter 358 and/or to the radio receiver 360. As anotherexample, the swarm manager 340 can additionally or alternativelyidentify the lead life jacket of the swarm network as the life jacketfrom among the multiple life jackets of the swarm network thatdemonstrates the greatest remaining battery energy. As yet anotherexample, the swarm manager 340 can alternatively randomly identifyand/or determine the lead life jacket of the swarm network. Furthermore,the swarm manager 340 of FIG. 3 can identify and/or determine multiple(e.g., different) life jackets of the swarm network as the lead lifejacket during the lifespan of the swarm network. For example, inresponse to a designated lead life jacket of the swarm network beingcompromised (e.g., due to destruction, loss of battery energy, loss ofsignal communication, etc.), the swarm manager 340 of FIG. 3 identifiesand/or determines a new lead life jacket of the swarm network. In somesuch examples, the swarm manager 340 is configured to seamlesslyidentify and/or determine the new lead life jacket without loss and/ordestruction of the existing swarm network.

The lead life jacket (e.g., the life jacket 300 of FIG. 3) of a swamnetwork (e.g., a swarm network generated and/or formed by the swarmmanager 340 of FIG. 3) receives and/or collects status data (e.g.,information, signals, notifications and/or reports indicating the statusof a life jacket) from the other (e.g., non-lead) life jackets of theswarm network, and transmits swarm status data (e.g., information,signals, notifications and/or reports indicating the status of multiplelife jackets of a swarm network) to one or more other device(s) (e.g., arescue vehicle, a cellular base station, a wireless access point, etc.).Thus, the lead life jacket of the swarm network functions and/oroperates as a gateway life jacket that transmits swarm status datarepresenting and/or indicating the status of the swarm network as awhole (e.g., inclusive of all members of the swarm network), as opposedto transmitting status data representing and/or indicating the status ofonly the lead life jacket. Swarm management data and/or swarm statusdata generated and/or processed by and/or at the swarm manager 340 canbe of any quantity, type, form and/or format, and can be stored in acomputer-readable storage medium such as the example memory 352 of FIG.3 described below.

FIG. 5A illustrates an example aircraft fuselage section 500 includingexample life jackets from which one or more example swarm networks canbe formed. In the illustrated example of FIG. 5A, the aircraft fuselagesection 500 includes seats organized in rows 1-9 and columns A-J, witheach seat including a life jacket located and/or stowed one or under theseat. In some examples, the jacket health evaluator 326 of FIG. 3determines that a first example life jacket 502 located at seat 1A isnot expired, and/or that a second example life jacket 506 located atseat 2J is expired. In some examples, the battery evaluator 336 of FIG.3 determines that a third example life jacket 506 located at seat 6J hasremaining battery energy that is below a battery energy threshold.

As further illustrated in FIG. 5A, multiple swarm networks can be formedby different life jackets commonly located within the aircraft fuselagesection 500. For example, a first example swarm network 508 formedwithin the aircraft fuselage section 500 includes a total of thirty lifejackets located at neighboring seats in rows 1-3 and columns A-J of theaircraft fuselage section 500, while a second example swarm network 510formed within the aircraft fuselage section 500 includes a total ofthree life jackets located at seats 6A, 8D and 9H of the aircraftfuselage section 500.

FIG. 5B illustrates another example aircraft fuselage section 550including example life jackets 552. As illustrated in FIG. 5B, stowedunder each seat is a life jacket 552 that is similar to the first,second and third life jackets 102, 104 and 106 of FIG. 1, and/or thelife jacket 300 of FIG. 3 described above. Each life jacket 552 has alife jacket controller 554, which includes a processor 556 (orprocessing elements) that is coupled to a battery 558 and to a radiotransmitter 560 (or a transceiver), as illustrated in the schematicdiagram in FIG. 5B. The processor 556 includes a program or instructionswhich when executed cause the processor 556 to intermittently check asensed battery voltage or energy level relative to a battery voltage orenergy threshold. Alternatively, a battery evaluator (e.g., the batteryevaluator 336 of FIG. 3) checks the battery energy level. The processor556 responsively generates a status signal that is transmitted by theradio transmitter 560, which includes information indicating the uniqueidentifier of the life jacket 552, the assigned storage location or seatlocation of the life jacket 552, a stowed state (or latent state)status, and information indicating that the battery voltage or energylevel is either acceptable or below the battery voltage or energy levelthreshold, where the signal information is received by areceiver/transceiver of a device in the aircraft cabin (such as device114 of FIG. 1). In an exemplary embodiment, the processor 556 is amicroprocessor that is operable in a low-power usage sleep-mode in whichthe processor 556 controls or limits the supply of current from battery558 to only the processor 556 and a timer function for periodicallywaking the processor 556, which then intermittently checks the batteryvoltage or energy level and responsively transmits a signal with batterylevel information, to thereby reduce battery power consumption andprolong the usable life of the battery 558. In the stowed or latentstate, the status of each life jacket 552 and its battery 558 may bedisplayed by a device within the aircraft cabin viewable by aircraftcrew, to notify crew of any life jacket 552 that is expired or thatneeds replacement of a battery 558.

As illustrated in FIG. 5B, each life jacket 552 stowed under a seat hasa processor 556 coupled to the battery 558 and to a motion sensor 562configured to detect motion of the life jacket 552. In the event of anaircraft water landing, each passenger or crew member preparing toevacuate may remove the life jacket 552 stowed under their seat. Thelife jacket 552 is positioned against the lower side of the seat andincludes a motion sensor 562 that senses motion, such as motion of thelife jacket 552 relative to the seat during removal of the life jacket552 from beneath the seat, for example. In one exemplary embodiment, themotion sensor 562 is an infrared sensor positioned to face the lowerside of the seat such that the seat covers the motion sensor 562 and themotion sensor 562 cannot detect motion. The motion sensor 562 could notdetect motion by a person for example, until the life jacket 552 isremoved from the seat and the motion sensor 562 detects motion of aperson through black-body radiation in contrast to background objects.The motion sensor 562 may include other suitable sensors that areconfigured to detect movement such as motion when the life jacket 552 isremoved from the seat. Upon sensing movement after removal of the lifejacket 552 from beneath the seat, the motion sensor 562 communicatessensed motion to the processor 556. In one exemplary embodiment, themotion sensor 562 communicates a signal to an enable input of theprocessor 556, for waking the processor 556 from a sleep mode andswitching the processor 556 to full power operation for applying powerto multiple sensors to be monitored, and to the radio transmitter 560(or transceiver for receiving signals). In response to communication ofsensed motion by the motion sensor 562, the processor 556 is configuredto communicate sensed motion information to the radio transmitter 560(or transceiver), which is configured to wirelessly communicate sensedmotion information associated with the life jacket 552, such that thecommunicated information is received by a life jacket controller 554 ofone or more other life jackets 552 that are within wireless signalrange.

Preferably, one or more (e.g., all) of the life jackets 552 has/have acontroller 554 that further includes an accelerometer in communicationwith the processor 556. The processor 556 may detect sensed motion ofthe life jacket 552 based on the acceleration data sensed by theaccelerometer that exceeds a threshold, or based on analysis ofaccelerometer data wirelessly communicated by other life jackets. Inresponse to detected or sensed motion of the life jacket 552 by theaccelerometer, the processor 556 is configured to communicateaccelerometer data to the radio transmitter 560 (or transceiver), whichis configured to wirelessly communicate accelerometer and/or motion dataassociated with the life jacket 552, such that the communicatedinformation is received by a life jacket controller 554 of one or moreother life jackets 552 that are within wireless signal range.

In an exemplary embodiment, the processor 556 includes instructionswhich when executed cause the processor 556 to implement a state manager568, where in response to detected or sensed motion of the life jacket552, the processor 556 and state manager 568 are configured totransition from the stowed state 570 (in which the processor 556performs limited monitoring and wireless communication to minimizebattery power consumption) to the motion state 572. During the motionstate 572, the processor 556 is configured to communicate informationincluding sensed motion from the motion sensor 562 to the radiotransmitter 560 (or transceiver), which is configured to wirelesslycommunicate signals including sensed motion information associated withthe life jacket 552, such that the communicated information is receivedby a life jacket controller 554 of one or more life jackets 552 that arewithin wireless signal range, such as life jackets 552 depicted in FIG.5B that are being removed from beneath seats by passengers who move intothe aisles to evacuate. In an exemplary embodiment, the life jacketcontroller 554 further includes a temperature sensor 564 configured todetect a temperature proximate the life jacket 552, which initially maybe an ambient temperature of the surrounding environment. When a userputs on the life jacket 552, the temperature sensor 564 of the lifejacket 552 being worn detects an increase in sensed temperature from aprior sensed ambient temperature, which is indicative that the lifejacket 552 is being in worn by a user. The processor 556 incommunication with the temperature sensor 564 is configured to detect atemperature increase, or a sensed temperature that is above or below athreshold temperature, which is indicative of the life jacket 552 beingworn by a user. Optionally, the life jacket controller 554 may furtherinclude an ambient temperature sensor, where the processor 556 isconfigured to compare the sensed temperature information sensed by thetemperature sensor 564 with the sensed ambient temperature, to determineif a temperature difference is indicative of the life jacket 552 beingworn by a user. In response to detecting a temperature increase ortemperature threshold indicative of the life jacket being worn by auser, the processor 556 and state manager 568 implemented by theprocessor 556 are configured to transition operation to the worn stateor installed state 574.

In an exemplary embodiment, the processor 556 and state manager 568implemented by the processor 556 are configured to transition from themotion state 572 to the worn state or installed state 574, in responseto a temperature increase or temperature threshold indicative of thelife jacket 552 being worn by a user. In the worn state or installedstate 574, the processor 556 is configured to monitor the sensedtemperature sensed by the temperature sensor 564, which is an indicatorthat the user is in good health. During the worn state or installedstate 574, the processor 556 is configured to communicate sensedtemperature information to the radio transmitter 560 (or transceiver),which is configured to wirelessly communicate signals including sensedtemperature information associated with the life jacket 552 being wornby a user and the user's health, such that the communicated informationis received by a life jacket controller 554 of one or more life jackets552 that are within wireless signal range. It should be noted that thewireless communications by the life jacket controllers for one or morelife jackets may communicate via one of a Bluetooth® interface, a nearfield communication (NFC) interface, a Wi-Fi communication network, aBluetooth communication network, a cellular network, a Zigbee network,or other suitable wireless communication protocols.

In an exemplary embodiment, the processor 556 and state manager 568implemented by the processor 556 that are configured to transition fromthe stowed state 570 and the motion state 572 are further configured tooperate in the worn state or installed state 574, and to cause theprocessor 556 to periodically communicate status information to betransmitted by the radio transmitter 560 (or transceiver). The processor556 directs the radio transmitter 560 (or transceiver) to transmitwireless signals including information indicating the unique identifierof the life jacket 552, the assigned storage location or seat locationof the life jacket 552, a worn state (or installed state) status, andinformation indicating the sensed temperature associated with the lifejacket 552 being worn and the user's health, where the signalinformation is received by a receiver/transceiver of a life jacketcontroller 554 of one or more life jackets 552 that are within wirelesssignal range. The transmitting life jacket controller 554 communicateswireless signal information that is received by one or more other lifejackets, such as those life jackets being worn by passengers in theaisles preparing to evacuate as depicted in FIG. 5B. Where thetransmitting life jacket controller 554 communicates wireless signalinformation that is received by one or more other life jackets 552, thetransmitted wireless signal sent by the transmitting life jacketcontroller 554 may prompt a request for a “lead life jacket”acknowledgement response communication from the one or more other lifejacket controllers, for purposes of establishing a communication networkbetween a number of life jacket controllers that are within wirelesscommunication range of each other. In one exemplary embodiment, if aparticular life jacket controller 554 in the worn state 574 is the firstto transmit wireless signal information received by one or more otherlife jacket controllers, upon receipt by the particular life jacketcontroller 554 of an acknowledgement response communication from one ormore other life jacket controllers, the particular first transmittinglife jacket controller 554 is established as the lead life jacket thatcontrols the formation and/or maintenance of a swarm network thatincludes the one or more other life jacket controllers. The processor556 of the one or more life jacket controllers may execute instructionsthat cause the processor 556 to operate a swarm manager application, forexample, for implementing the above process for requesting a “lead lifejacket” acknowledgement response communication and establishing aparticular life jacket controller 554 as a lead life jacket. The otherlife jacket controllers forming the swarm network continue to respond toand communicate their status information the lead life jacket controller554. As life jacket controllers of other life jackets 552 thattransition to the worn state 574 receive wireless communication signalstransmitted by the lead life jacket (which signals include informationidentifying the transmitting life jacket controller 554 as the lead lifejacket), other life jacket controllers are joined in the swarm networkof one or more life jacket controllers and life jackets 552. If for anyreason the life jacket controller 554 of the lead life jacket fails totransmit (within a predetermined time from the last transmission) asubsequent signal that identifies the transmitting life jacketcontroller as the lead life jacket, another one of the life jacketcontrollers is configured to transmit wireless signal information toprompt a request for a “lead life jacket” acknowledgement responsecommunication, for of establishing a new lead life jacket within thecommunication network between the life jacket controllers withinwireless communication range of each other. In this manner, a swarmnetwork may be formed by the one or more life jacket controllers of oneor more life jackets 552 being worn by users, such as those life jackets552 depicted in FIG. 5B that are being worn by passengers in the aislespreparing to evacuate.

In an exemplary embodiment, where the users or passengers in the aislesdepicted in FIG. 5B evacuate the aircraft and may enter a body of water,the one or more life jackets 552 further include a moisture sensor 566that senses and/or detects the extent to which the life jacket 552 isexposed to water. The moisture sensor 566 is in communication with theprocessor 556 of the life jacket controller 554, where the processor 556is configured to determine that the user or wearer of the life jacket552 is in water based on the sensed moisture detected by the moisturesensor 566. Where the processor 556 determines that the user or wearerof the life jacket 552 is in water based on the sensed moisture, theprocessor 556 and state manager 568 implemented by the processor 556 areconfigured to transition from the worn state or installed state 574 tothe immersed state 576.

In an exemplary embodiment, the processor 556 and state manager 568implemented by the processor 556 are configured to transition from theworn state or installed state 574 to the immersed state 576, in whichthe life jacket controller 554 is further configured to operate in theimmersed state 576 and cause the processor 556 to periodicallycommunicate status information to the radio transmitter 560 (ortransceiver) for transmission of signals with status information. Thelead life jacket controller 554 preferably establishes and/orcommunicates transmit schedule or timing for the one or more other lifejacket controllers to transmit status data. As other life jacketcontrollers transition from the worn state 574 to the immersed state 576when other users of life jackets enter the water, the other life jacketcontrollers continue to receive wireless communication signalstransmitted by the lead life jacket (which signals include informationidentifying the transmitting life jacket controller as the current leadlife jacket). The one or more other life jacket controllers in theimmersed state 576 transmit status information to the lead life jacketcontroller 554, which information includes the unique identifier of thelife jacket 552, the assigned storage location or seat location of thelife jacket 552, an immersion state status, and information indicatingthe sensed temperature associated with the life jacket 552 being wornand the user's health. The lead life jacket controller 554 alsotransmits information pertaining to the swarm status data for the one ormore life jackets in the immersion state 576 to one or more otherdevice(s) (e.g., a rescue vehicle, a cellular base station, a wirelessaccess point, etc.). The lead life jacket controller 554 also transmitsto rescue crew information pertaining to the swarm status data for theone or more life jackets 552 in the immersion state 576, whichinformation includes for each life jacket 552 in the swarm, the uniqueidentifier of the life jacket 552, the assigned storage location or seatlocation of the life jacket 552, an immersion state status, andinformation indicating the sensed temperature associated with the lifejacket 552 being worn and the user's health. In one exemplaryembodiment, one or more of the life jackets or life jacket controllerspreferably include a GPS receiver that receives location information,which includes the current latitude, longitude and altitude of the lifejacket 552. The lead life jacket controller 554 preferably furtherincludes a GPS receiver, and the processor 556 of the life jacketcontroller 554 is configured to receive the location informationreceived from the GPS receiver. The lead life jacket controller 554 isconfigured to include the location information for the one or more lifejackets in the transmission of swarm status information to one or moredevices of a rescue vehicle or crew. The designated lead life jacket, oranother life jacket controller that assumes the role of the lead lifejacket, are configured to continue communicating swarm statusinformation from the one or more other life jacket controllers to one ormore other device(s) (e.g., a rescue vehicle, a cellular base station, awireless access point, etc.) to facilitate prompt rescue of the users ofthe life jackets, where rescue may be prioritized based on their healthstatus.

FIG. 6 illustrates an example swarm network 600 operating in anenvironment in which several example life jackets of the swarm network600 are immersed in water. In the illustrated example of FIG. 6, theswarm network 600 includes a first example life jacket 602, a secondexample life jacket 604, a third example life jacket 606, a fourthexample life jacket 608, a fifth example life jacket 610, a sixthexample life jacket 612, and a seventh example life jacket 614. Thefirst, second, third, fourth and fifth life jackets 602, 604, 606, 608,610 of the swarm network 600 are immersed in water. The sixth andseventh life jackets 612, 614 of the swarm network 600 are not immersedin water, and are instead located aboard floatation vehicles (e.g.,rafts).

In the illustrated example of FIG. 6, respective user health evaluators(e.g., implemented as the user health evaluator 334 of FIG. 3) of thesixth and seventh life jackets 612, 614 have determined that therespective users of the sixth and seventh life jackets 612, 614 are ingood health, as indicated by the first example triage markers 616 ofFIG. 6. Respective user health evaluators (e.g., implemented as the userhealth evaluator 334 of FIG. 3) of the first and second life jackets602, 604 have determined that the respective users of the first andsecond life jackets 602, 604 are in fair health (e.g., less than goodhealth, but better than poor health), as indicated by the second exampletriage markers 618 of FIG. 6. Respective user health evaluators (e.g.,implemented as the user health evaluator 334 of FIG. 3) of the third,fourth and fifth life jackets 606, 608 and 610 have determined that therespective users of the third, fourth and fifth life jackets 606, 608and 610 are in poor health, as indicated by the third example triagemarkers 620 of FIG. 6.

As further shown in the illustrated example of FIG. 6, the first lifejacket 602 of FIG. 6 transmits communications to the third and fourthlife jackets 606, 608, and receives communications from the fifth lifejacket 610. The second life jacket 604 of FIG. 6 receives communicationsfrom the third and sixth life jackets 606, 612. The third life jacket606 of FIG. 6 transmits communications to the second, fourth and fifthlife jackets 604, 608, 610, and receives communication from the firstlife jacket 602. The fourth life jacket 608 of FIG. 6 transmitscommunications to the fifth and seventh life jackets 610, 614, andreceives communications from the first and third life jackets 602, 606.The fifth life jacket 610 of FIG. 6 transmits communications to thefirst life jacket 602, and receives communications from the third andfourth life jackets 606, 608. The sixth life jacket 612 of FIG. 6transmits communications to the second and seventh life jackets 604,614. The seventh life jacket 614 of FIG. 6 receives communications fromthe fourth and sixth life jackets 608, 612.

FIG. 7 illustrates a first example swarm network communication diagram700. The first swarm network communication diagram 700 of FIG. 7facilitates, enables, and/or governs communications between a firstexample life jacket 702, a second example life jacket 704, a thirdexample life jacket 706, a fourth example life jacket 708, an examplefloatation vehicle 710 (e.g., a raft), and an example rescue vehicle 712(e.g., a rescue boat, a rescue helicopter, etc.). In the illustratedexample of FIG. 7, the first life jacket 702 of FIG. 7 communicates withthe second and third life jackets 704, 706, and with the floatationvehicle 710. The second life jacket 704 of FIG. 7 communicates with thefirst, third and fourth life jackets 702, 706, 708, with the floatationvehicle 710, and with the rescue vehicle 712. The third life jacket 706of FIG. 7 communicates with the first, second and fourth life jackets702, 704, 708, and with the floatation vehicle 710. The fourth lifejacket 708 of FIG. 7 communicates with the second and third life jackets704, 706, and with the floatation vehicle 710. The floatation vehicle710 of FIG. 7 communicates with the first, second, third and fourth lifejackets 702, 704, 706, 708, and with the rescue vehicle 712. The rescuevehicle 712 of FIG. 7 communicates with the second life jacket 704, andwith the floatation vehicle 710.

FIG. 8 illustrates a second example swarm network communication diagram800. The second swarm network communication diagram 800 of FIG. 8facilitates, enables, and/or governs communications between a firstexample life jacket 802, a second example life jacket 804, a thirdexample life jacket 806, a fourth example life jacket 808, an examplefloatation vehicle 810 (e.g., a raft), and an example rescue vehicle 812(e.g., a rescue boat, a rescue helicopter, etc.). In the illustratedexample of FIG. 8, the first life jacket 802 of FIG. 8 communicates withthe second life jackets 804. The second life jacket 804 of FIG. 8communicates with the first and third life jackets 802, 806. The thirdlife jacket 806 of FIG. 8 communicates with the second and fourth lifejackets 804, 808, and with the rescue vehicle 812. The fourth lifejacket 808 of FIG. 8 communicates with the third life jackets 806. Thefloatation vehicle 810 of FIG. 8 communicates with the rescue vehicle812. The rescue vehicle 812 of FIG. 8 communicates with the third lifejacket 806, and with the floatation vehicle 810.

Returning to the illustrated example of FIG. 3, the status manager 342of FIG. 3 manages and/or controls the generation of status data (e.g.,information, signals, notifications and/or reports indicating the statusof a life jacket) for the life jacket 300 of FIG. 3. For example, thestatus manager 342 of FIG. 3 can generate status data based on and/orincluding a unique identifier of the life jacket 300, an assignedstorage location of the life jacket 300, and/or an expiration date ofthe life jacket 300 determined by the jacket identifier 322 of FIG. 3, alocation of the life jacket 300 determined by the location identifier324 of FIG. 3, jacket health data generated by the jacket healthevaluator 326 of FIG. 3, movement data generated by the movementevaluator 328 of FIG. 3, installation data generated by the installationevaluator 330 of FIG. 3, immersion data generated by the immersionevaluator 332 of FIG. 3, user health data generated by the user healthevaluator 334 of FIG. 3, battery energy data generated by the batteryevaluator 336 of FIG. 3, and/or operational state data generated by thestate manager 338 of FIG. 3. In some such examples (e.g., when a swarmnetwork has been generated and/or formed by the swarm manager 340 ofFIG. 3, as described above), the status data generated by the statusmanager 342 can be swarm status data (e.g., information, signals,notifications and/or reports indicating the status of multiple lifejackets of a swarm network) that, in addition to the above-describedinformation and/or data associated with the life jacket 300, alsoincludes corresponding information and/or data for one or more otherlife jacket(s) (e.g., one or more other life jacket(s) that, along withthe life jacket 300 of FIG. 3, form the swarm network).

In some examples, the status manager 342 of FIG. 3 generates theabove-described status data based on the state of the life jacket 300 asmanaged and/or determined by the state manager 338. For example, whenthe life jacket is in a stowed (e.g. latent) state, the status datagenerated by the status manager 342 can include a unique identifier ofthe life jacket 300, an assigned storage location of the life jacket300, and/or an expiration date of the life jacket 300 determined by thejacket identifier 322 of FIG. 3, a location of the life jacket 300determined by the location identifier 324 of FIG. 3, jacket health datagenerated by the jacket health evaluator 326 of FIG. 3, movement datagenerated by the movement evaluator 328 of FIG. 3, and/or operationalstate data generated by the state manager 338 of FIG. 3. As anotherexample, when the life jacket is in the motion state, the status datagenerated by the status manager 342 can further include installationdata generated by the installation evaluator 330 of FIG. 3. As anotherexample, when the life jacket is in the installed state, the status datagenerated by the status manager 342 can further include immersion datagenerated by the immersion evaluator 332 of FIG. 3. As another example,when the life jacket is in the immersed state, the status data generatedby the status manager 342 can further include user health data generatedby the battery evaluator 336 of FIG. 3.

Furthermore, the status manager 342 of FIG. 3 can generate theabove-described status data at multiple (e.g., different) predefinedintervals (e.g., sampling periods) based on the current state of thelife jacket 300, as managed and/or determined by the state manager 338of FIG. 3. For example, the status manager 342 can generate the statusdata according to a first predefined interval when the life jacket 300is in a stowed (e.g., latent) state, according to s second predefinedinterval (e.g., different from the first predefined interval) when thelife jacket 300 is in a motion state, according to a third predefinedinterval (e.g., different from each of the first and second predefinedintervals) when the life jacket 300 is in an installed state, andaccording to a fourth predefined interval (e.g., different from each ofthe first, second and third predefined intervals) when the life jacket300 is in an immersed state. Status management data and/or status datagenerated and/or processed by and/or at the status manager 342 can be ofany quantity, type, form and/or format, and can be stored in acomputer-readable storage medium such as the example memory 352 of FIG.3 described below.

The schedule manager 344 of FIG. 3 manages and/or controls a schedule(e.g., an order, a sequence, respective times, etc.) by which statusdata is to be transmitted from the life jacket 300 of FIG. 3. Forexample, the schedule manager 344 can establish and/or apply a schedulefor transmitting status data from the life jacket 300 to one or moreother device(s) e.g., a smartphone, a tablet, a laptop computer, adesktop computer, a server, another life jacket, a rescue vehicle, acellular base station, a wireless access point, etc.). As anotherexample, in instances where the life jacket 300 of FIG. 3 has beendesignated as a lead life jacket of a swarm network generated and/orformed by the swarm manager 340 of FIG. 3, the schedule manager 344 canestablish and/or apply a schedule for transmitting swarm status datafrom the life jacket 300 (e.g., the lead life jacket) to one or moreother device(s) (e.g., a rescue vehicle, a cellular base station, awireless access point, etc.).

The schedule manager 344 of FIG. 3 can establish and/or determine aschedule for transmitting status data using one or more evaluationand/or selection technique(s). For example, the schedule manger 344 canestablish and/or determine the schedule based on the available bandwidthof the network with which the network interface 350 of FIG. 3 isassociated, and/or based on the network communication protocoldetermined by the protocol manger 346 of FIG. 3. As another example, theschedule manger 344 can additionally or alternatively establish and/ordetermine the schedule based on the remaining battery energy of thebattery 302 of the life jacket 300. As yet another example, the schedulemanger 344 can alternatively randomly establish and/or determine theschedule.

Furthermore, the schedule manager 344 of FIG. 3 can establish, determineand/or apply determine multiple (e.g., different) schedules based on thecurrent state of the life jacket 300, as determined by the state manager338 of FIG. 3. For example, the schedule manager 344 can establish,determine and/or apply a first schedule when the life jacket 300 is in astowed (e.g., latent) state, a second schedule (e.g., different from thefirst schedule) when the life jacket 300 is in a motion state, a thirdschedule (e.g., different from each of the first and second schedules)when the life jacket 300 is in an installed state, and a fourth schedule(e.g., different from each of the first, second and third schedules)when the life jacket 300 is in an immersed state. Schedule managementdata and/or schedules managed, generated and/or processed by and/or atthe schedule manager 344 can be of any quantity, type, form and/orformat, and can be stored in a computer-readable storage medium such asthe example memory 352 of FIG. 3 described below.

The protocol manager 346 of FIG. 3 controls, manages and/or determines anetwork communication protocol to be implemented by the radiotransmitter 358 and/or the radio receiver 360 of FIG. 3, and/or, moregenerally, to be implemented by the network interface 350 of FIG. 3 toenable the life jacket 300 of FIG. 3 to operate and/or communicate withone or more other device(s) (e.g., a smartphone, a tablet, a laptopcomputer, a desktop computer, a server, another life jacket, a rescuevehicle, a cellular base station, a wireless access point, etc.). Insome examples, the network interface 350 of FIG. 3 can be configured toenable the life jacket 300 of FIG. 3 to implement only one type ofnetwork communication protocol (e.g., a single candidate protocol) tooperate and/or communicate with the other device(s). For example, thenetwork interface 350 of FIG. 3 can be configured to enable the lifejacket 300 of FIG. 3 to implement only a Wi-Fi communication protocol tooperate and/or communicate with the other device(s). In such examples,the protocol manager 346 of FIG. 3 identifies and/or determines thesingle candidate protocol as the network communication protocol to beimplemented by the radio transmitter 358 and/or the radio receiver 360of FIG. 3, and/or, more generally, to be implemented by the networkinterface 350 of FIG. 3.

In other examples, the network interface 350 of FIG. 3 can be configuredto enable the life jacket 300 of FIG. 3 to implement more than one typeof network communication protocol (e.g., multiple candidate protocols)to operate and/or communicate with the other device(s). For example, thenetwork interface 350 of FIG. 3 can be configured to enable the lifejacket 300 of FIG. 3 to implement any of a cellular communicationprotocol, a Wi-Fi communication protocol, a Bluetooth communicationprotocol, a Zigbee communication protocol, etc. to operate and/orcommunicate with the other device(s). In such examples, the protocolmanager 346 of FIG. 3 identifies and/or determines a selected one of themultiple candidate protocols as the network communication protocol to beimplemented by the radio transmitter 358 and/or the radio receiver 360of FIG. 3, and/or, more generally, to be implemented by the networkinterface 350 of FIG. 3. In some such examples, the protocol manager 346identifies and/or determines the network communication protocol as theprotocol from among the multiple candidate protocols that enables thegreatest signal strength for communications from the radio transmitter358 and/or to the radio receiver 360. Network communication protocoldata managed, determined and/or processed by and/or at the protocolmanager 346 can be of any quantity, type, form and/or format, and can bestored in a computer-readable storage medium such as the example memory352 of FIG. 3 described below.

The system interface 348 of FIG. 3 facilitates interactions and/orcommunications between a user and the life jacket 300 of FIG. 3. Thesystem interface 348 includes one or more input device(s) 354 via whichthe user can input information and/or data to the life jacket 300. Forexample, the input device(s) 354 can include a button, a switch, and/ora microphone that enable(s) the user to convey data and/or commands tothe jacket identifier 322, the state manager 338, the swarm manager 340,the status manager 342, the protocol manager 346, the network interface350, and/or the memory 352 of FIG. 3, and/or, more generally, to thelife jacket 300 of FIG. 3. The system interface 348 of FIG. 3 alsoincludes one or more output device(s) 356 via which the system interface348 presents information and/or data in visual, audible, and/or tactileform to the user. For example, the output device(s) 356 can include alight emitting diode and/or a liquid crystal display for presentingvisual information, a speaker for presenting audible information, and/ora haptic device for presenting tactile information. Data and/orinformation that is presented and/or received via the system interface348 can be of any quantity, type, form and/or format, and can be storedin a computer-readable storage medium such as the example memory 352 ofFIG. 3 described below.

The network interface 350 of FIG. 3 enables and/or facilitates one ormore network-based communication(s) (e.g., cellular communication(s),Wi-Fi communication(s), Bluetooth communication(s), Zigbeecommunication(s), etc.) between the life jacket 300 of FIG. 3 and one ormore other device(s) (e.g., a smartphone, a tablet, a laptop computer, adesktop computer, a server, another life jacket, a rescue vehicle, acellular base station, a wireless access point, etc.). As mentionedabove, the network interface 346 of FIG. 3 includes the radiotransmitter 358 and the radio receiver 360 of FIG. 3, each of which isfurther described below.

The radio transmitter 358 of FIG. 3 transmits data and/or one or moreradio frequency signal(s) to one or more other device(s) (e.g., asmartphone, a tablet, a laptop computer, a desktop computer, a server,another life jacket, a rescue vehicle, a cellular base station, awireless access point, etc.). In some examples, the data and/orsignal(s) transmitted by the radio transmitter 358 is/are communicatedover a network (e.g., a cellular network, a Wi-Fi network, a Bluetoothnetwork, a Zigbee network, etc.) utilizing a network communicationprotocol determined by the protocol manager 346 of FIG. 3. In someexamples, the radio transmitter 358 transmits data and/or one or moreradio frequency signal(s) based on status data and/or swarm status datagenerated by and/or at the status manager 342 of FIG. 3. In someexamples, the radio transmitter 358 transmits data and/or one or moreradio frequency signal(s) according to a schedule determined by theschedule manager 344 of FIG. 3. Data corresponding to the signal(s) tobe transmitted by the radio transmitter 358 can be of any type, formand/or format, and can be stored in a computer-readable storage mediumsuch as the example memory 352 of FIG. 3 described below.

The radio receiver 360 of FIG. 3 collects, acquires and/or receives dataand/or one or more radio frequency signal(s) from one or more otherdevice(s) (e.g., a smartphone, a tablet, a laptop computer, a desktopcomputer, a server, another life jacket, a rescue vehicle, a cellularbase station, a wireless access point, etc.). In some examples, the dataand/or signal(s) received by the radio receiver 360 is/are communicatedover a network (e.g., a cellular network, a Wi-Fi network, a Bluetoothnetwork, a Zigbee network, etc.) utilizing a network communicationprotocol determined by the protocol manager 346 of FIG. 3. In someexamples, the radio receiver 360 can receive status data from one ormore other (e.g., non-lead) life jacket(s) of a swarm network generatedand/or formed by the swarm manager 340 of FIG. 3. In some examples, theradio receiver 360 can receive data and/or signal(s) corresponding toone or more request(s) for data associated with the life jacket 300 ofFIG. 3. The one or more request(s) for data can be transmitted from oneor more other device(s) (e.g., a request from a smartphone, a tablet, alaptop computer, a desktop computer, a server, another life jacket, arescue vehicle, a cellular base station, a wireless access point, etc.).Data carried by, identified and/or derived from the signal(s) collectedand/or received by the radio receiver 360 can be of any type, formand/or format, and can be stored in a computer-readable storage mediumsuch as the example memory 352 of FIG. 3 described below.

The memory 352 of FIG. 3 can be implemented by any type(s) and/or anynumber(s) of storage device(s) such as a storage drive, a flash memory,a read-only memory (ROM), a random-access memory (RAM), a cache and/orany other physical storage medium in which information is stored for anyduration (e.g., for extended time periods, permanently, brief instances,for temporarily buffering, and/or for caching of the information). Theinformation stored in the memory 352 can be stored in any file and/ordata structure format, organization scheme, and/or arrangement.

In some examples, the memory 352 stores location signal data collectedand/or received by the GPS receiver 304 of FIG. 3, motion data sensed,measured and/or detected by the motion sensor 306 of FIG. 3,acceleration data sensed, measured and/or detected by the accelerometer308 of FIG. 3, ambient temperature data sensed, measured and/or detectedby the ambient temperature sensor 310 of FIG. 3, buckle connection datasensed, measured and/or detected by the buckle sensor 312 of FIG. 3,moisture data sensed, measured and/or detected by the moisture sensor314 of FIG. 3, body temperature data sensed, measured and/or detected bythe body temperature sensor 316 of FIG. 3, pulse data sensed, measuredand/or detected by the pulse sensor 318 of FIG. 3, and/or respirationdata sensed, measured and/or detected by the respiration sensor 320 ofFIG. 3. In some examples, the memory 352 stores a unique identifier ofthe life jacket 300, an assigned storage location (e.g., the intendedstowed position) of the life jacket 300, and/or an expiration date ofthe life jacket 300, as can be identified and/or determined by and/or atthe jacket identifier 322 of FIG. 3. In some examples, the memory storeslocation data identified and/or determined by and/or at the locationidentifier 324 of FIG. 3.

In some examples, the memory 352 stores jacket health evaluation dataand/or jacket health data evaluated, generated and/or processed byand/or at the jacket health evaluator 326 of FIG. 3, movement evaluationdata and/or movement data evaluated, generated and/or processed byand/or at the movement evaluator 328 of FIG. 3, installation evaluationdata and/or installation data evaluated, generated and/or processed byand/or at the installation evaluator 330 of FIG. 3, immersion evaluationdata and/or immersion data evaluated, generated and/or processed byand/or at the immersion evaluator 332 of FIG. 3, user health evaluationdata and/or user health data evaluated, generated and/or processed byand/or at the user health evaluator 334 of FIG. 3, and/or battery energyevaluation data and/or battery energy data evaluated, generated and/orprocessed by and/or at the battery evaluator 336 of FIG. 3.

In some examples, the memory 352 stores operational state managementdata and/or operational state data generated and/or processed by and/orat the state manager 338 of FIG. 3, swarm management data and/or swarmstatus data generated and/or processed by and/or at the swarm manager340 of FIG. 3, status management data and/or status data generatedand/or processed by and/or at the status manager 342 of FIG. 3, schedulemanagement data and/or schedules managed, generated and/or processed byand/or at the schedule manager 344 of FIG. 3, and/or networkcommunication protocol data managed, determined and/or processed byand/or at the protocol manager 346 of FIG. 3.

In some examples, the memory 352 stores data and/or information that ispresented and/or received via the input device(s) 354 and/or the outputdevice(s) 356 of FIG. 3, and/or, more generally, via the systeminterface 348 of FIG. 3. In some examples, the memory 352 stores datacorresponding to the signal(s) to be transmitted by the radiotransmitter 358 of the network interface 350 of FIG. 3, and/or datacarried by, identified and/or derived from the signal(s) collectedand/or received by the radio receiver 360 of the network interface 350of FIG. 3.

The memory 352 of FIG. 3 is accessible to the GPS receiver 304, themotion sensor 306, the accelerometer 308, the ambient temperature sensor310, the buckle sensor 312, the moisture sensor 314, the bodytemperature sensor 316, the pulse sensor 318, the respiration sensor320, the jacket identifier 322, the location identifier 324, the jackethealth evaluator 326, the movement evaluator 328, the installationevaluator 330, the immersion evaluator 332, the user health evaluator334, the battery evaluator 336, the state manager 338, the swarm manager340, the status manager 342, the schedule manger 344, the protocolmanager 346, the system interface 348 (including the input device(s) 354and the output device(s) 356) and/or the network interface 350(including the radio transmitter 358 and the radio receiver 360) of FIG.3, and/or, more generally, to the life jacket 300 of FIG. 3.

While an example manner of implementing the life jacket 300 isillustrated in FIG. 3, one or more of the elements, processes and/ordevices illustrated in FIG. 3 can be combined, divided, re-arranged,omitted, eliminated and/or implemented in any other way. Further, thebattery 302, the GPS receiver 304, the motion sensor 306, theaccelerometer 308, the ambient temperature sensor 310, the buckle sensor312, the moisture sensor 314, the body temperature sensor 316, the pulsesensor 318, the respiration sensor 320, the jacket identifier 322, thelocation identifier 324, the jacket health evaluator 326, the movementevaluator 328, the installation evaluator 330, the immersion evaluator332, the user health evaluator 334, the battery evaluator 336, the statemanager 338, the swarm manager 340, the status manager 342, the schedulemanager 344, the protocol manager 346, the system interface 348, thenetwork interface 350, the memory 352, the input device(s) 354, theoutput device(s) 356, the radio transmitter 358, the radio receiver 360,and/or, more generally, the example life jacket 300 of FIG. 3 can beimplemented by hardware, software, firmware and/or any combination ofhardware, software and/or firmware. Thus, for example, any of thebattery 302, the GPS receiver 304, the motion sensor 306, theaccelerometer 308, the ambient temperature sensor 310, the buckle sensor312, the moisture sensor 314, the body temperature sensor 316, the pulsesensor 318, the respiration sensor 320, the jacket identifier 322, thelocation identifier 324, the jacket health evaluator 326, the movementevaluator 328, the installation evaluator 330, the immersion evaluator332, the user health evaluator 334, the battery evaluator 336, the statemanager 338, the swarm manager 340, the status manager 342, the schedulemanager 344, the protocol manager 346, the system interface 348, thenetwork interface 350, the memory 352, the input device(s) 354, theoutput device(s) 356, the radio transmitter 358, the radio receiver 360,and/or, more generally, the example life jacket 300 of FIG. 3 could beimplemented by one or more analog or digital circuit(s), logiccircuit(s), programmable processor(s), programmable controller(s),graphics processing unit(s) (GPU(s)), digital signal processor(s)(DSP(s)), application specific integrated circuit(s) (ASIC(s)),programmable logic device(s) (PLD(s)) and/or field programmable logicdevice(s) (FPLD(s)). When reading any of the apparatus or system claimsof this patent to cover a purely software and/or firmwareimplementation, at least one of the battery 302, the GPS receiver 304,the motion sensor 306, the accelerometer 308, the ambient temperaturesensor 310, the buckle sensor 312, the moisture sensor 314, the bodytemperature sensor 316, the pulse sensor 318, the respiration sensor320, the jacket identifier 322, the location identifier 324, the jackethealth evaluator 326, the movement evaluator 328, the installationevaluator 330, the immersion evaluator 332, the user health evaluator334, the battery evaluator 336, the state manager 338, the swarm manager340, the status manager 342, the schedule manager 344, the protocolmanager 346, the system interface 348, the network interface 350, thememory 352, the input device(s) 354, the output device(s) 356, the radiotransmitter 358, the radio receiver 360, and/or, more generally, theexample life jacket 300 of FIG. 3 is/are hereby expressly defined toinclude a non-transitory computer-readable storage device or storagedisk including the software and/or firmware. Further still, the battery302, the GPS receiver 304, the motion sensor 306, the accelerometer 308,the ambient temperature sensor 310, the buckle sensor 312, the moisturesensor 314, the body temperature sensor 316, the pulse sensor 318, therespiration sensor 320, the jacket identifier 322, the locationidentifier 324, the jacket health evaluator 326, the movement evaluator328, the installation evaluator 330, the immersion evaluator 332, theuser health evaluator 334, the battery evaluator 336, the state manager338, the swarm manager 340, the status manager 342, the schedule manager344, the protocol manager 346, the system interface 348, the networkinterface 350, the memory 352, the input device(s) 354, the outputdevice(s) 356, the radio transmitter 358, the radio receiver 360,and/or, more generally, the example life jacket 300 of FIG. 3 caninclude one or more element(s), process(es) and/or device(s) in additionto, or instead of, those illustrated in FIG. 3, and/or can include morethan one of any or all of the illustrated elements, processes anddevices. As used herein, the phrase “in communication,” includingvariations thereof, encompasses direct communication and/or indirectcommunication through one or more intermediary component(s), and doesnot require direct physical (e.g., wired) communication and/or constantcommunication, but rather additionally includes selective communicationat periodic intervals, scheduled intervals, aperiodic intervals, and/orone-time events.

Flowcharts representative of example hardware logic, machine-readableinstructions, hardware implemented state machines, and/or anycombination thereof for implementing the life jacket 300 of FIG. 3 areshown in FIGS. 9-11. The machine-readable instructions can be one ormore executable program(s) or portion(s) of executable program(s) forexecution by a computer processor such as the example processor 1202shown in the example processor platform 1200 discussed below inconnection with FIG. 12. The program(s) can be embodied in softwarestored on a non-transitory computer-readable storage medium, or a memoryassociated with the processor 1202, but the entire program(s) and/orparts thereof could alternatively be executed by a device other than theprocessor 1202 and/or embodied in firmware or dedicated hardware.Further, although the example program(s) is/are described with referenceto the flowcharts illustrated in FIGS. 9-11, many other methods ofimplementing the example life jacket 300 of FIG. 3 can alternatively beused. For example, the order of execution of the blocks can be changed,and/or some of the blocks described can be changed, eliminated, orcombined. Additionally or alternatively, any or all of the blocks can beimplemented by one or more hardware circuit(s) (e.g., discrete and/orintegrated analog and/or digital circuitry, an FPGA, an ASIC, acomparator, an operational-amplifier (op-amp), a logic circuit, etc.)structured to perform the corresponding operation without executingsoftware or firmware.

The machine-readable instructions described herein can be stored in oneor more of a compressed format, an encrypted format, a fragmentedformat, a packaged format, etc. Machine-readable instructions asdescribed herein can be stored as data (e.g., portions of instructions,code, representations of code, etc.) that can be utilized to create,manufacture, and/or produce machine-executable instructions. Forexample, the machine-readable instructions can be fragmented and storedon one or more storage device(s) and/or computing device(s) (e.g.,servers). The machine-readable instructions can require one or more ofinstallation, modification, adaptation, updating, combining,supplementing, configuring, decryption, decompression, unpacking,distribution, reassignment, etc. in order to make them directly readableand/or executable by a computing device and/or other machine. Forexample, the machine-readable instructions can be stored in multipleparts, which are individually compressed, encrypted, and stored onseparate computing devices, wherein the parts when decrypted,decompressed, and combined form a set of executable instructions thatimplement a program such as that described herein. In another example,the machine-readable instructions can be stored in a state in which theycan be read by a computer, but require addition of a library (e.g., adynamic link library (DLL)), a software development kit (SDK), anapplication programming interface (API), etc. in order to execute theinstructions on a particular computing device or other device. Inanother example, the machine-readable instructions can need to beconfigured (e.g., settings stored, data input, network addressesrecorded, etc.) before the machine-readable instructions and/or thecorresponding program(s) can be executed in whole or in part. Thus, thedisclosed machine-readable instructions and/or corresponding program(s)are intended to encompass such machine-readable instructions and/orprogram(s) regardless of the particular format or state of themachine-readable instructions and/or program(s) when stored or otherwiseat rest or in transit.

As mentioned above, the example processes of FIGS. 9-11 can beimplemented using executable instructions (e.g., computer and/ormachine-readable instructions) stored on a non-transitory computerand/or machine-readable medium such as a flash memory, a read-onlymemory, a cache, a random-access memory and/or any other storage deviceor storage disk in which information is stored for any duration (e.g.,for extended time periods, permanently, for brief instances, fortemporarily buffering, and/or for caching of the information). As usedherein, the term non-transitory computer-readable medium is expresslydefined to include any type of computer-readable storage device and/orstorage disk and to exclude propagating signals and to excludetransmission media.

“Including” and “comprising” (and all forms and tenses thereof) are usedherein to be open ended terms. Thus, whenever a claim employs any formof “include” or “comprise” (e.g., comprises, includes, comprising,including, having, etc.) as a preamble or within a claim recitation ofany kind, it is to be understood that additional elements, terms, etc.can be present without falling outside the scope of the correspondingclaim or recitation. As used herein, when the phrase “at least” is usedas the transition term in, for example, a preamble of a claim, it isopen-ended in the same manner as the term “comprising” and “including”are open ended. The term “and/or” when used, for example, in a form suchas A, B, and/or C refers to any combination or subset of A, B, C such as(1) A alone, (2) B alone, (3) C alone, (4) A with B, (5) A with C, (6) Bwith C, and (7) A with B and with C. As used herein in the context ofdescribing structures, components, items, objects and/or things, thephrase “at least one of A and B” is intended to refer to implementationsincluding any of (1) at least one A, (2) at least one B, and (3) atleast one A and at least one B. Similarly, as used herein in the contextof describing structures, components, items, objects and/or things, thephrase “at least one of A or B” is intended to refer to implementationsincluding any of (1) at least one A, (2) at least one B, and (3) atleast one A and at least one B. As used herein in the context ofdescribing the performance or execution of processes, instructions,actions, activities and/or steps, the phrase “at least one of A and B”is intended to refer to implementations including any of (1) at leastone A, (2) at least one B, and (3) at least one A and at least one B.Similarly, as used herein in the context of describing the performanceor execution of processes, instructions, actions, activities and/orsteps, the phrase “at least one of A or B” is intended to refer toimplementations including any of (1) at least one A, (2) at least one B,and (3) at least one A and at least one B.

FIG. 9 is a flowchart representative of example machine-readableinstructions 900 that can be executed to implement the example lifejacket 300 of FIG. 3 to selectively operate the life jacket 300 in oneof multiple operational states of the life jacket 300. The exampleprogram 900 of FIG. 9 begins when the state manager 338 of FIG. 3operates the life jacket 300 in a stowed (e.g., latent) state (block902). In some examples, the state manager 338 of FIG. 3 enables and/oractivates one or more of the GPS receiver 304, the motion sensor 306,the accelerometer 308, the jacket identifier 322, the locationidentifier 322, the jacket health identifier 326, the movement evaluator328, and/or the battery evaluator 334 of the life jacket 300 of FIG. 3in connection with operating the life jacket 300 in the stowed state.

At block 904, the movement evaluator 328 of FIG. 3 determines whetherthe life jacket 300 of FIG. 3 has moved by more than a threshold amount.For example, the movement evaluator 328 of FIG. 3 can determine whetherthe life jacket 300 of FIG. 3 has moved by more than a threshold amountbased on data obtained from the motion sensor 306 and/or theaccelerometer 308 of FIG. 3. If the movement evaluator 328 of FIG. 3determines at block 904 that the life jacket 300 of FIG. 3 has not movedby more than a threshold amount, control of the example program 900 ofFIG. 9 remains at block 904. If the movement evaluator 328 of FIG. 3instead determines at block 904 that the life jacket 300 of FIG. 3 hasmoved by more than a threshold amount, control of the example program900 of FIG. 9 proceeds to block 906.

At block 906, the state manager 338 of FIG. 3 operates the life jacket300 in a motion state. In some examples, the state manager 338 of FIG. 3additionally or alternatively (e.g., relative to the stowed statedescribed above) enables and/or activates one or more of the ambienttemperature sensor 310, the buckle sensor 312, and/or the installationevaluator 330 of the life jacket 300 of FIG. 3 in connection withoperating the life jacket 300 in the motion state.

At block 908, the installation evaluator 330 of FIG. 3 determineswhether the life jacket 300 of FIG. 3 has been installed on a user. Forexample, the installation evaluator 330 of FIG. 3 can determine whetherthe life jacket 300 of FIG. 3 has been installed on a user based on dataobtained from the ambient temperature sensor 310 and/or the bucklesensor 312 of FIG. 3. If the installation evaluator 330 of FIG. 3determines at block 908 that the life jacket 300 of FIG. 3 has not beeninstalled on a user, control of the example program 900 of FIG. 9remains at block 908. If the installation evaluator 330 of FIG. 3instead determines at block 908 that the life jacket 300 of FIG. 3 hasbeen installed on a user, control of the example program 900 of FIG. 9proceeds to block 910.

At block 910, the state manager 338 of FIG. 3 operates the life jacket300 in an installed state. In some examples, the state manager 338 ofFIG. 3 additionally or alternatively (e.g., relative to the stowed stateand/or the motion state described above) enables and/or activates one ormore of the moisture sensor 314 and/or the immersion evaluator 332 ofthe life jacket 300 of FIG. 3 in connection with operating the lifejacket 300 in the installed state.

At block 912, the immersion evaluator 332 of FIG. 3 determines whetherthe life jacket 300 of FIG. 3 has been immersed in water. For example,the immersion evaluator 332 of FIG. 3 can determine whether the lifejacket 300 of FIG. 3 has been immersed in water based on data obtainedfrom the moisture sensor 314 of FIG. 3. If the immersion evaluator 332of FIG. 3 determines at block 912 that the life jacket 300 of FIG. 3 hasnot been immersed in water, control of the example program 900 of FIG. 9remains at block 912. If the immersion evaluator 332 of FIG. 3 insteaddetermines at block 912 that the life jacket 300 of FIG. 3 has beenimmersed in water, control of the example program 900 of FIG. 9 proceedsto block 914.

At block 914, the state manager 338 of FIG. 3 operates the life jacket300 in an immersed state. In some examples, the state manager 338 ofFIG. 3 additionally or alternatively (e.g., relative to the stowedstate, the motion state, and/or the installed state described above)enables and/or activates one or more of the body temperature sensor 316,the pulse sensor 318, the respiration sensor 320, and/or the user healthevaluator 334 of the life jacket 300 of FIG. 3 in connection withoperating the life jacket 300 in the installed state and/or the immersedstate.

At block 916, the state manager 338 of FIG. 3 determines whether todiscontinue operating the life jacket 300 of FIG. 3. For example, thestate manager 338 and/or, more generally, the life jacket 300 of FIG. 3can receive one or more user input(s) via the system interface 348 ofFIG. 3 indicating that operation of the life jacket 300 of FIG. 3 is tobe discontinued. If the state manager 338 of FIG. 3 determines at block916 that operation of the life jacket is not to be discontinued, controlof the example program 900 of FIG. 9 proceeds to block 918. If the statemanager 338 of FIG. 3 instead determines at block 916 that operation ofthe life jacket is to be discontinued, the example program 900 of FIG. 9ends.

At block 918, the battery evaluator 336 of FIG. 3 determines whether thelife jacket 300 of FIG. 3 has a threshold amount of battery energyremaining. For example, the battery evaluator 336 of FIG. 3 candetermine whether the battery 302 of the life jacket 300 of FIG. 3 has athreshold amount of energy remaining. If the battery evaluator 336 ofFIG. 3 determines at block 918 that the life jacket 300 of FIG. 3 has athreshold amount of battery energy remaining, control of the exampleprogram 900 of FIG. 9 returns to block 916. If the battery evaluator 336of FIG. 3 instead determines at block 918 that the life jacket 300 ofFIG. 3 does not have a threshold amount of battery energy remaining, alife jacket (e.g., the life jacket 300, and/or a lead life jacket of aswarm network) is notified, and the example program 900 of FIG. 9 ends.

FIG. 10 is a flowchart representative of example machine-readableinstructions 1000 that can be executed to implement the example lifejacket 300 of FIG. 3 to generate and transmit status data for the lifejacket 300. The example program 1000 of FIG. 10 begins when the jacketidentifier 322 of FIG. 3 identifies a unique identifier of the lifejacket 300 of FIG. 3 (block 1002). In some examples, the jacketidentifier 322 of FIG. 3 identifies a unique identifier (e.g., a serialnumber) of the life jacket 300 of FIG. 3 that differentiates the lifejacket 300 from other life jackets.

At block 1004, the jacket identifier 322 of FIG. 3 further identifies anassigned storage location of the life jacket 300 of FIG. 3. In someexamples, the jacket identifier 322 of FIG. 3 identifies an assignedposition, location and/or object (e.g., a seat number) at which the lifejacket 300 of FIG. 3 is stowed (or is to be stowed).

At block 1006, the jacket identifier 322 of FIG. 3 further identifies anexpiration date of the life jacket 300 of FIG. 3. In some examples, thejacket identifier 322 of FIG. 3 identifies the expiration date via anexpressly-defined expiration date of the life jacket 300 of FIG. 3, orvia an expiration date established based on an expressly-defined date ofmanufacture of the life jacket 300 of FIG. 3.

At block 1008, the location identifier 324 of FIG. 3 identifies alocation of the life jacket 300 of FIG. 3. In some examples, thelocation identifier 324 of FIG. 3 identifies the location of the lifejacket 300 of FIG. 3 by deriving the current location from the dataand/or signal(s) received by the GPS receiver 304 of FIG. 3.

At block 1010, the jacket health evaluator 326 of FIG. 3 generatesjacket health data for the life jacket 300 of FIG. 3. In some examples,the jacket health evaluator 326 of FIG. 3 generates jacket health datafor the life jacket 300 of FIG. 3 based on the expiration dateidentified and/or determined by the jacket identifier 322 of FIG. 3.

At block 1012, the movement evaluator 328 of FIG. 3 generates movementdata for the life jacket 300 of FIG. 3. In some examples, the movementevaluator 328 of FIG. 3 generates movement data for the life jacket 300of FIG. 3 based on motion data sensed, measured and/or detected by themotion sensor 306 of FIG. 3, and/or based on acceleration data sensed,measured and/or detected by the accelerometer 308 of FIG. 3.

At block 1014, the installation evaluator 330 of FIG. 3 generatesinstallation data for the life jacket 300 of FIG. 3. In some examples,the installation evaluator 330 of FIG. 3 generates installation data forthe life jacket 300 of FIG. 3 based on ambient temperature data sensed,measured and/or detected by the ambient temperature sensor 310 of FIG.3, and/or based on buckle connection data sensed, measured and/ordetected by the buckle sensor 312 of FIG. 3

At block 1016, the immersion evaluator 332 of FIG. 3 generates immersiondata for the life jacket 300 of FIG. 3. In some examples, the immersionevaluator 332 of FIG. 3 generates immersion data for the life jacket 300of FIG. 3 based on moisture data sensed, measured and/or detected by themoisture sensor 314 of FIG. 3.

At block 1018, the user health evaluator 334 of FIG. 3 generates userhealth data for the life jacket 300 of FIG. 3. In some examples, theuser health evaluator 334 of FIG. 3 generates user health data for thelife jacket 300 of FIG. 3 based on body temperature data sensed,measured and/or detected by the body temperature sensor 316 of FIG. 3,based on pulse data sensed, measured and/or detected by the pulse sensor318 of FIG. 3, and/or based on respiration data sensed, measured and/ordetected by the respiration sensor 320 of FIG. 3.

At block 1020, the battery evaluator 336 of FIG. 3 generates batteryenergy data for the life jacket 300 of FIG. 3. In some examples, thebattery evaluator 336 of FIG. 3 generates battery energy data for thelife jacket 300 of FIG. 3 based on a current state of charge of thebattery 302 of FIG. 3.

At block 1022, the state manager 338 of FIG. 3 generates operationalstate data for the life jacket 300 of FIG. 3. In some examples, thestate manager 338 of FIG. 3 generates operational state data for thelife jacket 300 of FIG. 3 based on the movement data generated by themovement evaluator 328 of FIG. 3, based on the installation datagenerated by the installation evaluator 330 of FIG. 3, and/or based onthe immersion data generated by the immersion evaluator 332 of FIG. 3.

At block 1024, the status manager 342 of FIG. 3 generates status datafor the life jacket 300 of FIG. 3 based on the unique identifier, theassigned storage location, the expiration date, the location, the jackethealth data, the movement data, the installation data, the immersiondata, the user health data, the battery data, and/or the operation statedata. In some examples, the information included within the status datagenerated by the status manager 342 of FIG. 3 is based on an operationalstate within which the life jacket 300 of FIG. 3 is operating at thetime the status manager 342 of FIG. 3 generates the status data.

At block 1026 the radio transmitter 358 of FIG. 3 transmits the statusdata to another device located remotely from the life jacket 300 of FIG.3. In some examples, the other device is a smartphone, a tablet, alaptop computer, a desktop computer, a server, another life jacket, arescue vehicle, a cellular base station, or a wireless access point. Insome examples, the radio transmitter 358 of FIG. 3 transmits the statusdata over a network (e.g., a cellular network, a Wi-Fi network, aBluetooth network, a Zigbee network, etc.) utilizing a networkcommunication protocol determined by the protocol manager 346 of FIG. 3.Following block 1026, the example program 1000 of FIG. 10 ends.

FIG. 11 is a flowchart representative of example machine-readableinstructions 1100 that can be executed to implement the example lifejacket 300 of FIG. 3 to generate and utilize a swarm network includingthe life jacket 300. The example program 1100 of FIG. 11 begins when theswarm manager 340 of FIG. 3 forms a swarm network including the lifejacket 300 of FIG. 3 and one or more other life jacket(s) (block 1102).In some examples, the swarm manager 340 of FIG. 3 forms the swarmnetwork while the life jacket 300 is in a stowed (e.g., latent) state.In some examples, the swarm network formed by the swarm manager 340 ofFIG. 3 includes a group of life jackets that are located on a vehicle(e.g., on an aircraft). In some examples, each life jacket of the swarmnetwork formed by the swarm manager 340 of FIG. 3 is structured and/orconfigured in a manner that enables the life jacket to transmit and/orreceive communications (e.g., radio signals and/or data) to and/or fromat least one of the other life jacket(s) of the swarm network.

At block 1104, the swarm manager 340 of FIG. 3 identifies a lead lifejacket of the swarm network. In some examples, the swarm manager 340 ofFIG. 3 identifies the life jacket 300 of FIG. 3 as the lead life jacketof the swarm network. In other examples, the swarm manager 340 of FIG. 3instead identifies one of the other life jacket(s) of the swarm networkas the lead life jacket of the swarm network. In some examples, theswarm manager 340 of FIG. 3 identifies the lead life jacket of the swarmnetwork as the life jacket from among the multiple life jackets of theswarm network that demonstrates the greatest signal strength for radiocommunications from the radio transmitter 358 and/or to the radioreceiver 360 of FIG. 3, and/or as the life jacket from among themultiple life jackets of the swarm network that demonstrates thegreatest remaining battery energy.

At block 1106, the swarm manager 340 of FIG. 3 determines whether thelife jacket 300 of FIG. 3 is the lead life jacket of the swarm network.If the swarm manager 340 of FIG. 3 determines at block 1106 that thelife jacket 300 of FIG. 3 is not the lead life jacket of the swarmnetwork, control of the example program 1100 of FIG. 11 proceeds toblock 1108. If the swarm manager 340 of FIG. 3 instead determines atblock 1106 that the life jacket 300 of FIG. 3 is the lead life jacket ofthe swarm network, control of the example program 1100 of FIG. 11proceeds to block 1110.

At block 1108, the radio transmitter 358 of FIG. 3 transmits status datafor the life jacket 300 of FIG. 3 to the lead life jacket of the swarmnetwork. In some examples, the radio transmitter 358 of FIG. 3 transmitsthe status data over a network (e.g., a cellular network, a Wi-Finetwork, a Bluetooth network, a Zigbee network, etc.) utilizing anetwork communication protocol determined by the protocol manager 346 ofFIG. 3. Following block 1108, the example program 1100 of FIG. 11 ends.

At block 1110, the radio receiver 360 of FIG. 3 collects status data forthe non-lead life jackets of the swarm network from one or more of thenon-lead life jacket(s) of the swarm network. In some examples, theradio receiver 360 of FIG. 3 collects the status data over a network(e.g., a cellular network, a Wi-Fi network, a Bluetooth network, aZigbee network, etc.) utilizing a network communication protocoldetermined by the protocol manager 346 of FIG. 3.

At block 1112, the radio transmitter 358 of FIG. 3 transmits swarmstatus data from the life jacket 300 of FIG. 3 (e.g., the lead lifejacket of the swarm network) to another device located remotely from thelife jacket 300 of FIG. 3, and/or located remotely from the swarmnetwork. In some examples, the other device is a rescue vehicle, acellular base station, or a wireless access point. In some examples, theradio transmitter 358 of FIG. 3 transmits the swarm status data over anetwork (e.g., a cellular network, a Wi-Fi network, a Bluetooth network,a Zigbee network, etc.) utilizing a network communication protocoldetermined by the protocol manager 346 of FIG. 3. Following block 1112,the example program 1100 of FIG. 11 ends.

FIG. 12 is a block diagram of an example processor platform 1200structured to execute the example machine-readable instructions 900 ofFIG. 9, the example machine-readable instructions 1000 of FIG. 10, andthe example machine-readable instructions 1100 of FIG. 11 to implementthe example life jacket 300 of FIG. 3. The processor platform 1200 ofthe illustrated example includes a processor 1202. The processor 1202 ofthe illustrated example is hardware. For example, the processor 1202 canbe implemented by one or more integrated circuit(s), logic circuit(s),microprocessor(s), GPU(s), DSP(s), microcontroller(s), processor(s), ormicrocontroller(s) from any desired family or manufacturer. The hardwareprocessor can be a semiconductor based (e.g., silicon based) device. Inthis example, the processor 1202 implements the example jacketidentifier 322, the example location identifier 324, the example jackethealth evaluator 326, the example movement evaluator 328, the exampleinstallation evaluator 330, the example immersion evaluator 332, theexample user health evaluator 334, the example battery evaluator 336,the example state manager 338, the example swarm manager 340, theexample status manager 342, the example schedule manager 344, and theexample protocol manager 346 of FIG. 3.

The processor 1202 of the illustrated example includes a local memory1204 (e.g., a cache). The processor 1202 is in communication with theexample battery 302 and the example GPS receiver 304 of FIG. 3, as wellas one or more example sensors 1206 (including the example motion sensor306, the example accelerometer 308, the example ambient temperaturesensor 310, the example buckle sensor 312, the example moisture sensor314, the example body temperature sensor 316, the example pulse sensor318, and the example respiration sensor 320 of FIG. 3) via a bus 1208.The processor 1202 is also in communication with a main memory includinga volatile memory 1210 and a non-volatile memory 1212 via the bus 1208.The volatile memory 1210 can be implemented by Synchronous DynamicRandom Access Memory (SDRAM), Dynamic Random Access Memory (DRAM),RAMBUS® Dynamic Random Access Memory (RDRAM®) and/or any other type ofrandom access memory device. The non-volatile memory 1214 can beimplemented by flash memory and/or any other desired type of memorydevice. Access to the main memory 1210, 1212 is controlled by a memorycontroller. In the illustrated example of FIG. 12, one or more of thevolatile memory 1210 and/or the non-volatile memory 1214 implement(s)the example memory 352 of FIG. 3.

The processor platform 1200 of the illustrated example also includes asystem interface circuit 1214. The system interface circuit 1214 can beimplemented by any type of interface standard, such as an Ethernetinterface, a universal serial bus (USB), a Bluetooth® interface, a nearfield communication (NFC) interface, and/or a PCI express interface. Inthe illustrated example, one or more input device(s) 354 of FIG. 3 areconnected to the system interface circuit 1214. The input device(s) 354permit(s) a user to enter data and/or commands into the processor 1202.The input device(s) 354 can be implemented by, for example, a button, aswitch, and/or a microphone. One or more output device(s) 356 of FIG. 3are also connected to the system interface circuit 1214 of theillustrated example. The output device(s) 356 can be implemented, forexample, by a light emitting diode and/or a liquid crystal display forpresenting visual information, a speaker for presenting audibleinformation, and/or a haptic device for presenting tactile information.In the illustrated example, the input device(s) 354, the outputdevice(s) 356, and the system interface circuit 1214 collectivelyimplement the example system interface 348 of FIG. 3.

The processor platform 1200 of the illustrated example also includes anetwork interface circuit 1216. The network interface circuit 1216 canbe implemented by any type of interface standard, such as an Ethernetinterface, a universal serial bus (USB), a Bluetooth® interface, a nearfield communication (NFC) interface, and/or a PCI express interface. Inthe illustrated example of FIG. 12, the network interface circuit 1216includes the example radio transmitter 358 and the example radioreceiver 360 of FIG. 3 to facilitate the exchange of data and/or signalswith other devices (e.g., a smartphone, a tablet, a laptop computer, adesktop computer, a server, another life jacket, a rescue vehicle, acellular base station, a wireless access point, etc.) via a network 1218(e.g., a cellular network, a Wi-Fi network, a Bluetooth network, aZigbee network, etc.).

Coded instructions 1220 including the machine-readable instructions 900of FIG. 9, the machine-readable instructions 1000 of FIG. 10, and themachine-readable instructions 1100 of FIG. 11 can be stored in the localmemory 1204, in the volatile memory 1210, in the non-volatile memory1214, and/or on a removable non-transitory computer-readable storagemedium such as a flash memory stick.

From the foregoing, it will be appreciated that digital life jackets andassociated methods have been disclosed that advantageously include anarray and/or collection of sensor(s) and/or processing element(s) thatare individually and/or collectively configured to determine and/orgenerate transmittable status data indicating whether the life jackethas moved (e.g., relative to an assigned storage location) by more thana threshold amount, whether the life jacket has been installed (e.g.,placed on and/or connected to) a user, whether the life jacket has beenimmersed in water, and/or user health status associated with a userwearing the life jacket. Such detailed status data can advantageously betransmitted from example digital life jackets disclosed herein to rescuevehicles and/or services to inform such rescue vehicles and/or servicesin a manner that can be of critical importance and/or assistance withregard to implementing efficient rescue efforts. Example digital lifejackets disclosed herein are networkable with one another. In thisregard, example digital life jackets disclosed herein are advantageouslystructured and/or configured to communicate with one another via a swarmnetwork formed by two or more of the life jackets. Example digital lifejackets disclosed herein identify a lead life jacket (e.g., a gatewaylife jacket) for the swarm network. The lead life jacket transmits swarmstatus data that includes status data for all members of the swarmnetwork, thereby advantageously increasing the efficiency of search andrescue efforts, and also advantageously reducing the amount of powerconsumed by the non-lead members of the swarm network.

In some examples, a life jacket is disclosed. In some disclosedexamples, the life jacket comprises a state manager and a swarm manager.In some disclosed examples, the state manager is configured toselectively operate the life jacket in one of multiple operationalstates of the life jacket based on data obtained from one or moresensors of the life jacket. In some disclosed examples, the swarmmanager is configured to form a swarm network including the life jacketand one or more other life jackets.

In some disclosed examples of the life jacket, the one or more sensorsinclude at least one of a motion sensor, an accelerometer, a temperaturesensor, a buckle sensor, a moisture sensor, or a physiologic sensor.

In some disclosed examples of the life jacket, the multiple operationalstates include a stowed state and at least one of a motion state, aninstalled state, or an immersed state.

In some disclosed examples, the life jacket further comprises a movementevaluator configured to determine whether the life jacket has moved bymore than a threshold amount. In some disclosed examples, the statemanager is configured to operate the life jacket in the stowed stateprior to the movement evaluator determining that the life jacket hasmoved by more than the threshold amount.

In some disclosed examples of the life jacket, the state manager isconfigured to operate the life jacket in the motion state in response tothe movement evaluator determining that the life jacket has moved bymore than the threshold amount.

In some disclosed examples, the life jacket further comprises aninstallation evaluator configured to determine whether the life jackethas been installed on a user. In some disclosed examples, the statemanager is configured to operate the life jacket in the installed statein response to the installation evaluator determining that the lifejacket has been installed on the user.

In some disclosed examples, the life jacket further comprises animmersion evaluator configured to determine whether the life jacket hasbeen immersed in water. In some disclosed examples, the state manager isconfigured to operate the life jacket in the immersed state in responseto the immersion evaluator determining that the life jacket has beenimmersed in the water.

In some disclosed examples of the life jacket, the swarm manager isconfigured to form the swarm network while the life jacket is operatingin the stowed state.

In some disclosed examples, the life jacket further comprises a statusmanager configured to generate status data for the life jacket. In somedisclosed examples, the life jacket further comprises a transmitterconfigured to transmit the status data from the life jacket to anotherdevice located remotely from the life jacket.

In some disclosed examples of the life jacket, the status data includesat least one of a unique identifier, an assigned storage location, anexpiration date, a location, jacket health data, movement data,installation data, immersion data, user health data, battery energydata, or operational state data of the life jacket.

In some disclosed examples of the life jacket, the swarm manager isconfigured to identify a lead life jacket of the swarm network fromamong the life jacket and the one or more other life jackets of theswarm network. In some disclosed examples, the lead life jacket is totransmit swarm status data from the lead life jacket to a remotelylocated rescue vehicle. In some disclosed examples, the swarm statusdata is to indicate a respective status for the life jacket and for eachof the one or more other life jackets of the swarm network.

In some examples, a method is disclosed. In some disclosed examples, themethod comprises selectively operating a life jacket, by executing acomputer-readable instruction with one or more processors of the lifejacket, in one of multiple operational states of the life jacket basedon data obtained from one or more sensors of the life jacket. In somedisclosed examples, the method further comprises forming a swarm networkincluding the life jacket and one or more other life jackets.

In some disclosed examples of the method, the one or more sensorsinclude at least one of a motion sensor, an accelerometer, a temperaturesensor, a buckle sensor, a moisture sensor, or a physiologic sensor.

In some disclosed examples of the method, the multiple operationalstates include a stowed state and at least one of a motion state, aninstalled state, or an immersed state.

In some disclosed examples, the method further comprises determining, byexecuting a computer-readable instruction with the one or moreprocessors, whether the life jacket has moved by more than a thresholdamount. In some disclosed examples, the method further comprisesoperating the life jacket in the stowed state prior to determining thatthe life jacket has moved by more than the threshold amount.

In some disclosed examples, the method further comprises operating thelife jacket in the motion state in response to determining that the lifejacket has moved by more than the threshold amount.

In some disclosed examples, the method further comprises determining, byexecuting a computer-readable instruction with the one or moreprocessors, whether the life jacket has been installed on a user. Insome disclosed examples, the method further comprises operating the lifejacket in the installed state in response to determining that the lifejacket has been installed on the user.

In some disclosed examples, the method further comprises determining, byexecuting a computer-readable instruction with the one or moreprocessors, whether the life jacket has been immersed in water. In somedisclosed examples, the method further comprises operating the lifejacket in the immersed state in response to determining that the lifejacket has been immersed in the water.

In some disclosed examples of the method, forming the swarm networkoccurs while the life jacket is operating in the stowed state.

In some disclosed examples, the method further comprises generating, byexecuting a computer-readable instruction with the one or moreprocessors, status data for the life jacket. In some disclosed examples,the method further comprises transmitting, by executing acomputer-readable instruction with the one or more processors, thestatus data from the life jacket to another device located remotely fromthe life jacket.

In some disclosed examples of the method, the status data includes atleast one of a unique identifier, an assigned storage location, anexpiration date, a location, jacket health data, movement data,installation data, immersion data, user health data, battery energydata, or operational state data of the life jacket.

In some disclosed examples, the method further comprises identifying, byexecuting a computer-readable instruction with the one or moreprocessors, a lead life jacket of the swarm network from among the lifejacket and the one or more other life jackets of the swarm network. Insome disclosed examples, the lead life jacket is to transmit swarmstatus data from the lead life jacket to a remotely located rescuevehicle. In some disclosed examples, the swarm status data is toindicate a respective status for the life jacket and for each of the oneor more other life jackets of the swarm network.

In some examples, a non-transitory computer-readable medium comprisinginstructions is disclosed. In some disclosed examples, the instructions,when executed, cause one or more processors of a life jacket toselectively operate the life jacket in one of multiple operationalstates of the life jacket based on data obtained from one or moresensors of the life jacket. In some disclosed examples, theinstructions, when executed, further cause the one or more processors toform a swarm network including the life jacket and one or more otherlife jackets.

In some disclosed examples of the non-transitory computer-readablestorage medium, the one or more sensors include at least one of a motionsensor, an accelerometer, a temperature sensor, a buckle sensor, amoisture sensor, or a physiologic sensor.

In some disclosed examples of the non-transitory computer-readablestorage medium, the multiple operational states include a stowed stateand at least one of a motion state, an installed state, or an immersedstate.

In some disclosed examples, the instructions, when executed, cause theone or more processors to determine whether the life jacket has moved bymore than a threshold amount. In some disclosed examples, theinstructions, when executed, cause the one or more processors to operatethe life jacket in the stowed state prior to determining that the lifejacket has moved by more than the threshold amount.

In some disclosed examples, the instructions, when executed, cause theone or more processors to operate the life jacket in the motion state inresponse to determining that the life jacket has moved by more than thethreshold amount.

In some disclosed examples, the instructions, when executed, cause theone or more processors to determine whether the life jacket has beeninstalled on a user. In some disclosed examples, the instructions, whenexecuted, cause the one or more processors to operate the life jacket inthe installed state in response to determining that the life jacket hasbeen installed on the user.

In some disclosed examples, the instructions, when executed, cause theone or more processors to determine whether the life jacket has beenimmersed in water. In some disclosed examples, the instructions, whenexecuted, cause the one or more processors to operate the life jacket inthe immersed state in response to determining that the life jacket hasbeen immersed in the water.

In some disclosed examples, the instructions, when executed, cause theone or more processors to form the swarm network while the life jacketis operating in the stowed state.

In some disclosed examples, the instructions, when executed, cause theone or more processors to generate status data for the life jacket. Insome disclosed examples, the instructions, when executed, cause the oneor more processors to transmit the status data from the life jacket toanother device located remotely from the life jacket.

In some disclosed examples of the non-transitory computer-readablestorage medium, the status data includes at least one of a uniqueidentifier, an assigned storage location, an expiration date, alocation, jacket health data, movement data, installation data,immersion data, user health data, battery energy data, or operationalstate data of the life jacket.

In some disclosed examples, the instructions, when executed, cause theone or more processors to identify a lead life jacket of the swarmnetwork from among the life jacket and the one or more other lifejackets of the swarm network. In some disclosed examples, the lead lifejacket is to transmit swarm status data from the lead life jacket to aremotely located rescue vehicle. In some disclosed examples, the swarmstatus data is to indicate a respective status for the life jacket andfor each of the one or more other life jackets of the swarm network.

In some disclosed examples, the instructions, when executed, cause theone or more processors to generate vital signs status data for anindividual on whom the life jacket is installed. In some disclosedexamples, the instructions, when executed, cause the one or moreprocessors to transmit the vital signs status data from the life jacketto another device located remotely from the life jacket.

Although certain example methods, apparatus and articles of manufacturehave been disclosed herein, the scope of coverage of this patent is notlimited thereto. On the contrary, this patent covers all methods,apparatus and articles of manufacture fairly falling within the scope ofthe claims of this patent.

1. A life jacket, comprising: a state manager configured to selectivelyoperate the life jacket in one of multiple operational states of thelife jacket based on data obtained from one or more sensors of the lifejacket; and a swarm manager configured to form a swarm network includingthe life jacket and one or more other life jackets.
 2. The life jacketof claim 1, wherein the one or more sensors include at least one of amotion sensor, an accelerometer, a temperature sensor, a buckle sensor,a moisture sensor, or a physiologic sensor.
 3. The life jacket of claim1, wherein the multiple operational states include a stowed state and atleast one of a motion state, an installed state, or an immersed state.4. The life jacket of claim 3, further comprising a movement evaluatorconfigured to determine whether the life jacket has moved by more than athreshold amount, wherein the state manager is configured to operate thelife jacket in the stowed state prior to the movement evaluatordetermining that the life jacket has moved by more than the thresholdamount.
 5. The life jacket of claim 4, wherein the state manager isconfigured to operate the life jacket in the motion state in response tothe movement evaluator determining that the life jacket has moved bymore than the threshold amount.
 6. The life jacket of claim 3, furthercomprising an installation evaluator configured to determine whether thelife jacket has been installed on a user, wherein the state manager isconfigured to operate the life jacket in the installed state in responseto the installation evaluator determining that the life jacket has beeninstalled on the user.
 7. The life jacket of claim 3, further comprisingan immersion evaluator configured to determine whether the life jackethas been immersed in water, wherein the state manager is configured tooperate the life jacket in the immersed state in response to theimmersion evaluator determining that the life jacket has been immersedin the water.
 8. The life jacket of claim 3, wherein the swarm manageris configured to form the swarm network while the life jacket isoperating in the stowed state.
 9. The life jacket of claim 1, furthercomprising: a status manager configured to generate status data for thelife jacket; and a transmitter configured to transmit the status datafrom the life jacket to another device located remotely from the lifejacket.
 10. The life jacket of claim 9, wherein the status data includesat least one of a unique identifier, an assigned storage location, anexpiration date, a location, jacket health data, movement data,installation data, immersion data, user health data, battery energydata, or operational state data of the life jacket.
 11. life jacket ofclaim 9, wherein the swarm manager is configured to identify a lead lifejacket of the swarm network from among the life jacket and the one ormore other life jackets of the swarm network, the lead life jacket totransmit swarm status data from the lead life jacket to a remotelylocated rescue vehicle, the swarm status data to indicate a respectivestatus for the life jacket and for each of the one or more other lifejackets of the swarm network.
 12. A method, comprising: selectivelyoperating a life jacket, by executing a computer-readable instructionwith one or more processors of the life jacket, in one of multipleoperational states of the life jacket based on data obtained from one ormore sensors of the life jacket; and forming a swarm network includingthe life jacket and one or more other life jackets.
 13. method of claim12, wherein the one or more sensors include at least one of a motionsensor, an accelerometer, a temperature sensor, a buckle sensor, amoisture sensor, or a physiologic sensor.
 14. The method of claim 12,wherein the multiple operational states include a stowed state and atleast one of a motion state, an installed state, or an immersed state.15. The method of claim 14, further comprising: determining, byexecuting a computer-readable instruction with the one or moreprocessors, whether the life jacket has moved by more than a thresholdamount; and operating the life jacket in the stowed state prior todetermining that the life jacket has moved by more than the thresholdamount.
 16. The method of claim 15, further comprising operating thelife jacket in the motion state in response to determining that the lifejacket has moved by more than the threshold amount.
 17. The method ofclaim 14, further comprising: determining, by executing acomputer-readable instruction with the one or more processors, whetherthe life jacket has been installed on a user; and operating the lifejacket in the installed state in response to determining that the lifejacket has been installed on the user.
 18. The method of claim 14,further comprising: determining, by executing a computer-readableinstruction with the one or more processors, whether the life jacket hasbeen immersed in water; and operating the life jacket in the immersedstate in response to determining that the life jacket has been immersedin the water.
 19. The method of claim 14, wherein forming the swarmnetwork occurs while the life jacket is operating in the stowed state.20. The method of claim 12, further comprising: generating, by executinga computer-readable instruction with the one or more processors, statusdata for the life jacket; and transmitting, by executing acomputer-readable instruction with the one or more processors, thestatus data from the life jacket to another device located remotely fromthe life jacket.
 21. The method of claim 20, wherein the status dataincludes at least one of a unique identifier, an assigned storagelocation, an expiration date, a location, jacket health data, movementdata, installation data, immersion data, user health data, batteryenergy data, or operational state data of the life jacket.
 22. Themethod of claim 20, further comprising identifying, by executing acomputer-readable instruction with the one or more processors, a leadlife jacket of the swarm network from among the life jacket and the oneor more other life jackets of the swarm network, the lead life jacket totransmit swarm status data from the lead life jacket to a remotelylocated rescue vehicle, the swarm status data to indicate a respectivestatus for the life jacket and for each of the one or more other lifejackets of the swarm network. 23-34. (canceled)